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 2019/11/02 04:28:08 UTC
[GitHub] [pulsar-client-go] tuteng commented on issue #81: Add reconnect
timeout after unload topic
tuteng commented on issue #81: Add reconnect timeout after unload topic
URL: https://github.com/apache/pulsar-client-go/pull/81#issuecomment-549009567
> Is it just printing the error message, right? The reconnection logic should go through after that.
>
> I think the initial sleep is actually correct, in the sense that we don’t want to immediately aggressively reconnect. The chances of the topic being ready immediately after a failover are thin.
>
> Though the 1sec sleep is too big. It will impose that latency spike on the produced messages. In the Java and C++ clients we’re actually using a 100ms initial back off delay, and then double it after that.
>
> One other option is to convert the loop into first sleeping and then trying, rather than the reverse
What I have observed now is that after the topic unload, it tries to reconnect. As a result, the broker-side Topic is in a fence state, causing the reconnection to fail. Then produce hang lives and do not send data. I did not have this problem using the java client
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services