nicoloboschi edited a comment on pull request #14097: URL: https://github.com/apache/pulsar/pull/14097#issuecomment-1028312716
The consequence of the issue is on the Consumer side. The problem (and actually the fix) resides on the broker side. If you have a Pulsar 2.8.x cluster with `transactionCoordinatorEnabled=true` and a client (2.8.x or 2.9.x) uses `enableTransaction=false`, everything works fine. The client is able to produce and consume (even without creating a transaction). If you have a Pulsar 2.9.x cluster with `transactionCoordinatorEnabled=true` and a client (2.8.x or 2.9.x) uses `enableTransaction=false`, the producer will produce the message correctly but, on the broker side, the BK client will read with a wrong position (-1, which means you never get an entry). The situation will be unblocked if a new writes happens into the topic (this is a supposition). I figured out the initial fix wasn't the right direction. I force-pushed and simplified the solution. (and updated the PR description) -- 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]
