[DISCUSS] Mitigate possibility of out of order messages

Hi Pulsar Community, I discovered a race condition in Pulsar’s Java Client ProducerImpl that can lead to messages persisted out-of-order for a single producer sending to a non-partitioned topic. I can reproduce this issue, and I verified the order by adding sequence ids to the message payload befo

[GitHub] [pulsar-helm-chart] sijie merged pull request #174: Fixes #173 Support both Role Binding and Cluster Role Binding dependi…

sijie merged pull request #174: URL: https://github.com/apache/pulsar-helm-chart/pull/174 -- 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. To unsubscribe, e-mail: dev-unsu

[GitHub] [pulsar-helm-chart] sijie closed issue #173: Helm Chart does not allow us deploy more another Pulsar instance with the same name in a different namespaces

sijie closed issue #173: URL: https://github.com/apache/pulsar-helm-chart/issues/173 -- 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. To unsubscribe, e-mail: dev-unsubscr.