Open WilliamDEdwards opened 1 year ago
3.3 is out of support. Could you please check whether this is reproducible in 3.5 or main branch?
3.3 is out of support.
Perhaps it would be useful to get supported versions into Debian backports.
Could you please check whether this is reproducible in 3.5 or main branch?
No, I will not be able to anytime soon.
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.
What happened?
One of the following issues occurs:
This happens on most stops and restarts, but not every. So far, there is no visible pattern.
I run an etcd cluster with the following nodes:
etcd0
etcd1
etcd2
Each cluster node also runs an etcd gateway.
Example:
At 11:51:09, I stopped the etcd gateway on
etcd2
:At exactly this moment (11:51:09),
etcd-gateway
also stops onetcd1
. 1 second later (11:51:10),etcd-gateway
also stops onetcd0
.What did you expect to happen?
When an etcd gateway is shut down, other etcd gateways should not be shut down.
How can we reproduce it (as minimally and precisely as possible)?
See 'What happened?'.
Anything else we need to know?
No response
Etcd version (please run commands below)
Etcd configuration (command line flags or environment variables)
Etcd debug information (please run commands below, feel free to obfuscate the IP address or FQDN in the output)
N/A
Relevant log output