New issue
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
Watch API. blocked forever even with WithRequireLeader option #17611
Labels
area/clientv3
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
type/bug
Comments
Duplicated with this issue: #12534 |
346999452
pushed a commit
to 346999452/etcd
that referenced
this issue
Mar 21, 2024
Signed-off-by: Hanying Gan [email protected]
346999452
pushed a commit
to 346999452/etcd
that referenced
this issue
Mar 21, 2024
Signed-off-by: Hanying Gan <[email protected]>
346999452
pushed a commit
to 346999452/etcd
that referenced
this issue
Mar 21, 2024
Signed-off-by: [email protected] <[email protected]>
jmhbnz
added
area/clientv3
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
labels
Mar 27, 2024
@346999452 can you close this issue if it is a duplicate? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/clientv3
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
type/bug
Bug report criteria
What happened?
watch api blocked forever even with WithRequireLeader option
What did you expect to happen?
no matter how the etcd server changes leader and restarts, as long as WithRequireLeader is set, it won't blocked
How can we reproduce it (as minimally and precisely as possible)?
Anything else we need to know?
clientv3/watch.go/run may
Etcd version (please run commands below)
golang client version : v0.0.0-20200520232829-54ba9589114f
server version : etcd Version: 3.4.16
Etcd configuration (command line flags or environment variables)
No response
Etcd debug information (please run commands below, feel free to obfuscate the IP address or FQDN in the output)
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: