You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a problem at line 512 of client.go where it should not break when there are no err.
If other goroutines are slow, context canceled will occur.
But this problem does not affect normal use.
What did you expect to happen?
No error output.
How can we reproduce it (as minimally and precisely as possible)?
Thanks @happlins for raising this issue. It looks like a real issue to me. The loop you pointed out should only break when err != nil. It means there is no need to wait for the result of other endpoints, because it will return an error anyway.
What happened?
etcd client v3: v3.5.4
I get an error when I initialize the client.
When I change
RejectOldCluster
to false everything works fine.There is a problem at line 512 of
client.go
where it should not break when there are no err.If other goroutines are slow, context canceled will occur.
But this problem does not affect normal use.
What did you expect to happen?
No error output.
How can we reproduce it (as minimally and precisely as possible)?
step 1
docker-compose.yaml
:step 2
Initialize client.
Anything else we need to know?
No response
Etcd version (please run commands below)
Etcd configuration (command line flags or environment variables)
paste your configuration here
Etcd debug information (please run commands blow, feel free to obfuscate the IP address or FQDN in the output)
Relevant log output
The text was updated successfully, but these errors were encountered: