michaeljmarshall commented on issue #19457: URL: https://github.com/apache/pulsar/issues/19457#issuecomment-1423392356
I am able to reproduce the errors by running the test on tag `v2.11.0`, but not on a recent commit of master. I wonder if this has already been fixed? These changes seem related: https://github.com/apache/pulsar/pull/15413. They were only just introduced in the 2.11 client, and the error messages suggest incorrect ordering of sequence ids. Here is the server side code that is leading to the error: https://github.com/apache/pulsar/blob/82237d3684fe506bcb6426b3b23f413422e6e4fb/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/persistent/MessageDeduplication.java#L358-L362 https://github.com/apache/pulsar/blob/82237d3684fe506bcb6426b3b23f413422e6e4fb/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/persistent/MessageDeduplication.java#L358-L362 We are getting the `Unknown` status and then hitting the default case. I am not able to troubleshoot this more until tomorrow, but hopefully we already have the fix and just need to get it released in 2.11.1. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
