Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
0.9.0.0, 0.10.2.0
-
None
-
None
-
None
Description
Currently in our test env, we found after one of the broker node crash(reboot or os crash), the client maybe still connecting to the crash node to send metadata request or other request, and it need about several minutes to aware the connection is timeout then try another node to connect to send the request. Then the client may still not aware the metadata change after several minutes.
We don't have a connection timeout for the network client, we should add a connection timeout for the client
