Hello David, Thanks for the KIP. For the described issue, I'm wondering if it can be resolved by tuning the CONNECTIONS_MAX_IDLE_MS_CONFIG ( connections.max.idle.ms) on the client side? Default is 9 minutes.
Guozhang On Tue, May 2, 2017 at 8:22 AM, 东方甲乙 <254479...@qq.com> wrote: > Hi all, > > Currently in our test environment, we found that after one of the broker > node crash (reboot or os crash), the client may still be connecting to the > crash node to send metadata request or other request, and it needs several > minutes to be aware that the connection is timeout then try another node to > connect to send the request. Then the client may still not be aware of the > metadata change after several minutes. > > > So I want to add a connect timeout on the client, please take a look at： > > https://cwiki.apache.org/confluence/display/KAFKA/KIP- > 148%3A+Add+a+connect+timeout+for+client > > Regards, > > David -- -- Guozhang
