afire007 opened a new issue #6712: Pulsar Go Client 2.4.1, 2.4.2 does not round robin messages by default for multi partitioned topics URL: https://github.com/apache/pulsar/issues/6712 **Describe the bug** The Pulsar Go Client does not properly round robin requests when sending data to a multi partitioned topic. This is observed consistently even when explicitly configuring round robin mode in pulsar go producer configuration settings. **To Reproduce** Steps to reproduce the behavior: 1. Start pulsar docker container 2. Create go client and publish messages to a multi-partitioned pulsar topic ./pulsar-admin non-persistent create-partitioned-topic \ non-persistent://gkiv/sample-topic/sample-topic-1min \ --partitions 6 Output when publishing: Consistently shows a single producer Id. { "msgRateIn" : 3512.4684755313106, "msgThroughputIn" : 446373.6632635517, "msgRateOut" : 0.0, "msgThroughputOut" : 0.0, "averageMsgSize" : 127.08260321068498, "storageSize" : 0, "publishers" : [ { "msgRateIn" : 3512.4684755313106, "msgThroughputIn" : 446373.6632635517, "averageMsgSize" : 126.83333333333333, "producerId" : 0 } ], "subscriptions" : { }, "replication" : { }, "metadata" : { "partitions" : 6 }, "partitions" : { } } **Expected behavior** Client should open a separate producer for each partition for the given topic it is publishing to, similar to the java client. This is resulting in extremely poor performance for producing messages to pulsar using the go client. **Screenshots** If applicable, add screenshots to help explain your problem. **Desktop (please complete the following information):** - Linux/Docker **Additional context** Add any other context about the problem here.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
