This means that in Pulsar's default round-robin routing mode, messages without a key are not assigned to partitions one-by-one in strict rotation. Instead, all messages collected during a batching interval are sent to the same partition, and only after the batch is sent does the producer switch to the next partition. This batching-aware approach improves throughput by maximizing batch size. If a message has a key, the key is hashed and always routed to the same partition, regardless of batching or round-robin settings. See
Pulsar routing modes documentation for details.
Would you like a step-by-step example or more technical detail?
Sources:
-
Pulsar routing modes documentation 👍 0 button 👎 0 button 💡
Hint: Mention @runllm in the thread for followups.