MonicaMagoniCom opened a new issue #9699: URL: https://github.com/apache/pulsar/issues/9699
We are using Pulsar in our cloud environment (deployed with Kubernetes). Pulsar is configured in **key_shared** mode subscription and it happens that when the traffic is higher than usual (in our case, Pulsar suddendly receives 300 messages), messages which have the same key are mapped to a different consumers. This lasts for the duration of the traffic peak, than the situation is restored and the messages with the same key are normally deliver to their right consumer. In our environment this causes an Optimistic Lock Exception, since 2 messages with the same key arrives at 2 different consumers, and they both try to update the same document in MongoDB. **To Reproduce** Pulsar 2.6.2 Key_shared mode Sudden peak of traffic **Expected behavior** I expect that messages with the same key are delivered to the same consumer, also when traffic increases. ---------------------------------------------------------------- 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]
