@RunLLM How does the broker configuration field

brokerDeduplicationMaxNumberOfProducers

work?

The

brokerDeduplicationMaxNumberOfProducers

field sets the maximum number of producers for which the broker will keep deduplication information. This means the broker tracks up to this number of producers to filter out duplicate messages; if the number of producers exceeds this limit, deduplication info for the oldest or inactive producers may be discarded, potentially allowing duplicates from those producers to be accepted again. The default value is 10,000 producers, and it can be configured in the broker settings or via the relevant configuration file according to StreamNative documentation and Pulsar documentation. Would you like more detail on how this interacts with producer activity or deduplication performance? Sources: - StreamNative: Quota & Deduplication Settings - Pulsar: Message Deduplication 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@RunLLM Does the broker configuration field

brokerDeduplicationMaxNumberOfProducers

count partition producers?

It seems likely that

brokerDeduplicationMaxNumberOfProducers

counts each internal producer created for a partitioned topic as a separate producer. For example, if you have a partitioned topic with 100 partitions and create one producer, Pulsar internally creates 100 producers—one per partition—which are all counted toward this limit, as described in Pulsar's partitioned topic documentation. Would you like more detail on how this affects deduplication or producer scaling? Sources: - Pulsar: Partitioned Topics and Lazy Producers 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.