michaeljmarshall edited a comment on issue #9916: URL: https://github.com/apache/pulsar/issues/9916#issuecomment-806361743
> @michaeljmarshall We can close the original consumer after check the DLQ has enough messages? That is essentially what we're currently doing in the test. We consume all of the messages from the DLQ and then close the two clients. I think we're seeing flakiness here because of the race condition in the consumer client. We publish messages to the DLQ topic and then we ack those messages on the original topic. If we close the consumer after sending a message to the DLQ topic and before acknowledging the message, this test will fail. Regarding my earlier comment about using transactions, it looks like the transaction client isn't available in the consumer client class. I am going to look into delaying the closing of the client if there are outstanding messages to be ack'ed -- 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]
