We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We see etcdserver: rpc not supported for learner error from clients with AutoSync enabled. https://github.com/etcd-io/etcd/blob/main/client/v3/client.go#L188 here does not exclude learner endpoint
etcdserver: rpc not supported for learner
Either requests are not sent to learner endpoints only or learner endpoints proxy requests to non learner member
Add a new member but do not promote it, and wait for client autosync to pick the new member
No response
etcdctl version: 3.5.0 API version: 3.5
$ etcdctl member list -w table # paste output here $ etcdctl --endpoints=<member list> endpoint status -w table # paste output here
The text was updated successfully, but these errors were encountered:
There is a PR in flight #13837
Sorry, something went wrong.
Fix will be available in v3.5.3
No branches or pull requests
What happened?
We see
etcdserver: rpc not supported for learner
error from clients with AutoSync enabled. https://github.com/etcd-io/etcd/blob/main/client/v3/client.go#L188 here does not exclude learner endpointWhat did you expect to happen?
Either requests are not sent to learner endpoints only or learner endpoints proxy requests to non learner member
How can we reproduce it (as minimally and precisely as possible)?
Add a new member but do not promote it, and wait for client autosync to pick the new member
Anything else we need to know?
No response
Etcd version (please run commands below)
etcdctl version: 3.5.0
API version: 3.5
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
No response
The text was updated successfully, but these errors were encountered: