etcd shutdown failed due to grpc: addrConn.createTransport connection error #11208
Comments
|
Also seeing with same with 3.3.18, the only way to recover is to sigkill the etcd process: 2020-01-30 18:21:33.629070 I | etcdmain: etcd Version: 3.3.18 2020-01-30 18:15:47.785992 N | pkg/osutil: received terminated signal, shutting down... Is there a fix for this in 3.4? |
|
same problem |
|
Hi, |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 21 days if no further activity occurs. Thank you for your contributions. |
Specific:
etcd Version: 3.3.0+git
Git SHA: Not provided (use ./build instead of go build)
Go Version: go1.12.5
Go OS/Arch: linux/amd64
but we use clientV2.
etcd cluster deployment
issue was happened on single node shutdown phase.
loop print addrConn.createTransport connection error, and etcd server process can't exit after received sigterm.
logs:
Sep 25 14:08:28 node1 etcd[2864]: received terminated signal, shutting down...
Sep 25 14:08:28 node1 etcd-start-up.sh[2864]: WARNING: 2019/09/25 14:08:28 grpc:
addrConn.createTransport failed to connect to {127.0.0.1:2379 0 }. Err :connection error:
desc = "transport: Error while dialing dial tcp 127.0.0.1:2379: connect: connection refused".
Reconnecting...
...
Sep 25 14:09:14 node1 etcd-start-up.sh[2864]: WARNING: 2019/09/25 14:09:14 grpc:
addrConn.createTransport failed to connect to {127.0.0.1:2379 0 }. Err :connection error:
desc = "transport: Error while dialing dial tcp 127.0.0.1:2379: connect: connection refused".
Reconnecting...
-- Reboot --
Reproducible:
yes, but low, observe 2+ cases by reboot command.
I searched history issues, and found it's similar with #8267, could you confirm whether same one or a new case? thanks!
what we do / WR for this issue:
we currently set TimeoutStopSec to low value to speed etcd service exit by sigkill.
The text was updated successfully, but these errors were encountered: