Version v3.1 of the documentation is no longer actively maintained. The page that you are viewing is the last archived version. For the latest stable documentation, see v3.5.
This is an alpha feature, we are looking for early feedback.
The gRPC proxy is a stateless etcd reverse proxy operating at the gRPC layer (L7). The proxy is designed to reduce the total processing load on the core etcd cluster. For horizontal scalability, it coalesces watch and lease API requests. To protect the cluster against abusive clients, it caches key range requests.
The gRPC proxy supports multiple etcd server endpoints. When the proxy starts, it randomly picks one etcd server endpoint to use. This endpoint serves all requests until the proxy detects an endpoint failure. If the gRPC proxy detects an endpoint failure, it switches to a different endpoint, if available, to hide failures from its clients. Other retry policies, such as weighted round-robin, may be supported in the future.
Scalable watch API
The gRPC proxy coalesces multiple client watchers (
c-watchers) on the same key or range into a single watcher (
s-watcher) connected to an etcd server. The proxy broadcasts all events from the
s-watcher to its
Assuming N clients watch the same key, one gRPC proxy can reduce the watch load on the etcd server from N to 1. Users can deploy multiple gRPC proxies to further distribute server load.
In the following example, three clients watch on key A. The gRPC proxy coalesces the three watchers, creating a single watcher attached to the etcd server.
+-------------+ | etcd server | +------+------+ ^ watch key A (s-watcher) | +-------+-----+ | gRPC proxy | <-------+ | | | ++-----+------+ |watch key A (c-watcher) watch key A ^ ^ watch key A | (c-watcher) | | (c-watcher) | +-------+-+ ++--------+ +----+----+ | client | | client | | client | | | | | | | +---------+ +---------+ +---------+
To effectively coalesce multiple client watchers into a single watcher, the gRPC proxy coalesces new
c-watchers into an existing
s-watcher when possible. This coalesced
s-watcher may be out of sync with the etcd server due to network delays or buffered undelivered events. When the watch revision is unspecified, the gRPC proxy will not guarantee the
c-watcher will start watching from the most recent store revision. For example, if a client watches from an etcd server with revision 1000, that watcher will begin at revision 1000. If a client watches from the gRPC proxy, may begin watching from revision 990.
Similar limitations apply to cancellation. When the watcher is cancelled, the etcd server’s revision may be greater than the cancellation response revision.
These two limitations should not cause problems for most use cases. In the future, there may be additional options to force the watcher to bypass the gRPC proxy for more accurate revision responses.
Scalable lease API
Abusive clients protection
The gRPC proxy caches responses for requests when it does not break consistency requirements. This can protect the etcd server from abusive clients in tight for loops.
Start etcd gRPC proxy
Consider an etcd cluster with the following static endpoints:
Start the etcd gRPC proxy to use these static endpoints with the command:
$ etcd grpc-proxy start --endpoints=infra0.example.com,infra1.example.com,infra2.example.com --listen-addr=127.0.0.1:2379
The etcd gRPC proxy starts and listens on port 8080. It forwards client requests to one of the three endpoints provided above.
Sending requests through the proxy:
$ ETCDCTL_API=3 ./etcdctl --endpoints=127.0.0.1:2379 put foo bar OK $ ETCDCTL_API=3 ./etcdctl --endpoints=127.0.0.1:2379 get foo foo bar
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.