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/01/10 14:26:00 UTC

[GitHub] [pulsar] wolfstudy edited a comment on pull request #13245: Make sure the client can get response when encounter producer busy exception.

wolfstudy edited a comment on pull request #13245:
URL: https://github.com/apache/pulsar/pull/13245#issuecomment-1008922786


   Thanks @codelipenghui 
   This problem is very much like a problem encountered by the Go SDK community recently, and all the phenomena seem to match the description in this pr.
   
   Through tcpdump, it was found that Go SDK sent ProducerCommand to the broker every time it reconnected, but the broker did not reply any Response to the client side, which caused the Go SDK to fail to reconnect until the entire client service was restarted.
   
   The broker version: branch-2.7.2
   go SDK version: new master
   
   And the issue refer to: https://github.com/apache/pulsar-client-go/issues/697


-- 
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