Closed perhapszzy closed 8 years ago
by the way, some times (not always). some worker may report
E0625 12:21:16.511111376 3825 tcp_client_posix.c:191] failed to connect to 'ipv4:180.101.191.78:30002': timeout occurred
but if it failed to connect the server, why the server log still shows the log above? And most of the workers (or most of the time) the code just stuck at the prepare_or_wait_for_session
step and output nothing,
Seems to be duplicate of #2472
Environment info
Operating System: Kubernetes/Ubuntu 14.04
Steps to reproduce
What have you tried?
prepare_or_wait_for_session
. However, it seems that logs suggest other workers are actually executing.Log is here and the code is here: