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
{{ message }}
This repository has been archived by the owner on Aug 21, 2020. It is now read-only.
I do a watch for a key prefix with client.watch_prefix('prefix'). The server is an etcd gateway (the TCP proxy).
It turns out etcd3-gateway doesn't handle at least two error cases:
when I restart the (upstream) etcd nodes, the etcd gateway closes the JSON streaming "array" and ends the connection with: {"error":{"grpc_code":14,"http_code":503,"message":"rpc error: code = Unavailable desc = transport is closing","http_status":"Service Unavailable"}}
when I cut the etcd gateway's TCP connections to the upstream servers it just closes the HTTP connection
Currently etcd3-gateway handles none of these, making the watch call hang forever.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I do a watch for a key prefix with client.watch_prefix('prefix'). The server is an etcd gateway (the TCP proxy).
It turns out etcd3-gateway doesn't handle at least two error cases:
Currently etcd3-gateway handles none of these, making the watch call hang forever.
The text was updated successfully, but these errors were encountered: