gRPC naming and discovery

go-grpc: for resolving gRPC endpoints with an etcd backend

etcd provides a gRPC resolver to support an alternative name system that fetches endpoints from etcd for discovering gRPC services. The underlying mechanism is based on watching updates to keys prefixed with the service name.

Using etcd discovery with go-grpc

The etcd client provides a gRPC resolver for resolving gRPC endpoints with an etcd backend. The resolver is initialized with an etcd client:

  1. import (
  2.     "go.etcd.io/etcd/v3/clientv3"
  3.     resolver "go.etcd.io/etcd/client/v3/naming/resolver"
  5.     "google.golang.org/grpc"
  6. )
  8. cli, cerr := clientv3.NewFromURL("http://localhost:2379")
  9. etcdResolver, err := resolver.NewBuilder(cli);
  10. conn, gerr := grpc.Dial("etcd:///foo/bar/my-service", grpc.WithResolvers(etcdResolver))

Managing service endpoints

The etcd resolver treats all keys under the prefix of the resolution target following a “/” (e.g., “foo/bar/my-service/“) with JSON-encoded (historically go-grpc naming.Update) values as potential service endpoints. Endpoints are added to the service by creating new keys and removed from the service by deleting keys.

Adding an endpoint

New endpoints can be added to the service through etcdctl:

  1. ETCDCTL_API=3 etcdctl put foo/bar/my-service/1.2.3.4 '{"Addr":"1.2.3.4","Metadata":"..."}'

The etcd client’s endpoints.Manager method can also register new endpoints with a key matching the Addr:

  2. em := endpoints.NewManager(client, "foo/bar/my-service")
  3. err := em.AddEndpoint(context.TODO(),"foo/bar/my-service/e1", endpoints.Endpoint{Addr:"1.2.3.4"});

Deleting an endpoint

Hosts can be deleted from the service through etcdctl:

  1. ETCDCTL_API=3 etcdctl del foo/bar/my-service/1.2.3.4

The etcd client’s endpoints.Manager method also supports deleting endpoints:

  1. em := endpoints.NewManager(client, "foo/bar/my-service")
  2. err := em.DeleteEndpoint(context.TODO(), "foo/bar/my-service/e1");

Registering an endpoint with a lease

Registering an endpoint with a lease ensures that if the host can’t maintain a keepalive heartbeat (e.g., its machine fails), it will be removed from the service:

  1. lease=`ETCDCTL_API=3 etcdctl lease grant 5 | cut -f2 -d' '`
  2. ETCDCTL_API=3 etcdctl put --lease=$lease my-service/1.2.3.4 '{"Addr":"1.2.3.4","Metadata":"..."}'
  3. ETCDCTL_API=3 etcdctl lease keep-alive $lease

In the golang:

  1. em := endpoints.NewManager(client, "foo/bar/my-service")
  2. err := endpoints.AddEndpoint(context.TODO(), "foo/bar/my-service/e1", endpoints.Endpoint{Addr:"1.2.3.4"});

Atomically updating endpoints

If it’s desired to modify multiple endpoints in a single transaction, endpoints.Manager can be used directly:

  1. em := endpoints.NewManager(c, "foo")
  3. err := em.Update(context.TODO(), []*endpoints.UpdateWithOpts{
  4.     endpoints.NewDeleteUpdateOpts("foo/bar/my-service/e1", endpoints.Endpoint{Addr: "1.2.3.4"}),
  5.     endpoints.NewAddUpdateOpts("foo/bar/my-service/e1", endpoints.Endpoint{Addr: "1.2.3.14"})})

Last modified June 14, 2021: Renaming content/en/next folder to content/en/v3.5. Updating redirects, links, and config as needed. (#363) (138926b)