You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2022/02/08 07:55:25 UTC

[GitHub] [pulsar] congbobo184 commented on pull request #14097: Consumer not able to consume message outside of a transaction if `enableTransaction=false` (client) and `TransactionCoordinatorEnabled=true` (broker) after 2.9.0

congbobo184 commented on pull request #14097:
URL: https://github.com/apache/pulsar/pull/14097#issuecomment-1032310651


   @nicoloboschi hi, I don't think we should return the Exception from broker to client when producer connect. In order to don't let disable transaction producer connect broker wait `transactionBuffer` recover. Maybe we can create a future filed in `TopicTransactionBuffer` like `transactionBufferFuture`. When `TopicTransactionBuffer` check the snapshot exist or not completely, we can complete this future then the producer can connect. In this way, we don't need to return exception to client and client don't need to reconnect.


-- 
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: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org