dial-timeout option does not take effect on the watch command. #18335
Labels
area/clientv3
area/etcdctl
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?
I don't have etcd-server running locally, and I have specified dial-timeout as 2s,but etcdctl keep stuck, which makes people wonder if the connection is successful but the data is not updated.
What did you expect to happen?
If the specified dial-timeout is exceeded and the endpoints cannot be connected, an error is returned.
How can we reproduce it (as minimally and precisely as possible)?
the endpoint targets are not running etcd-server, and running follow command:
Anything else we need to know?
get
command working wellEtcd version (please run commands below)
Etcd configuration (command line flags or environment variables)
paste your configuration here
Etcd debug information (please run commands below, 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: