Stanislaw Makarawec
10/17/2025, 10:59 AMRunLLM
10/17/2025, 10:59 AMreplicationProducerQueueSize parameter sets the queue size for the replicator producer in Pulsar. When changed dynamically, it only affects newly added replicators; for existing replicators, you must delete and recreate them for the new value to take effect. This parameter helps control memory usage and replication throughput between clusters.
Would you like more detail?
Sources:
- support dynamic config for replicationProducerQueueSize
- ServiceConfiguration.java 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.Stanislaw Makarawec
10/17/2025, 11:12 AMRunLLM
10/17/2025, 11:12 AMreplicationProducerQueueSize parameter. This parameter controls how many messages can be buffered in memory for replication before being sent to a remote cluster, so the ideal value depends on your workload, available broker memory, replication latency, and throughput requirements. You may want to consider factors such as the average message size, the number of topics being replicated, and the available memory on your brokers; monitoring broker memory usage and replication performance while adjusting this value can help you find a suitable setting. If this doesn't help, please reach out to the StreamNative support team for further assistance. 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.Stanislaw Makarawec
10/17/2025, 11:31 AMRunLLM
10/17/2025, 11:31 AMreplicationProducerQueueSize itself, but you can monitor related replication metrics such as backlog, throughput, and rate to infer if the queue size is appropriate. Metrics like pulsar_replication_backlog, pulsar_replication_rate_out, and pulsar_replication_throughput_out help track replication performance and can indicate if the queue is a bottleneck or underutilized, but the actual queue size in use is not directly exposed as a metric.
Would you like more detail?
Sources:
- Replication metrics
- ReplicationMetrics.java 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.