Skip to content
This repository has been archived by the owner on Aug 21, 2020. It is now read-only.

Watch doesn't handle error cases #13

Open
bra-fsn opened this issue Jan 8, 2018 · 0 comments
Open

Watch doesn't handle error cases #13

bra-fsn opened this issue Jan 8, 2018 · 0 comments

Comments

@bra-fsn
Copy link

bra-fsn commented Jan 8, 2018

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:

  1. 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"}}
  2. 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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant