kubernetes/vendor/go.etcd.io/etcd/clientv3
Ed Bartosh 016eb06d8b go.mod: update etcd to fix e2e tests
Updated etcd to v3.4.10 to include this fix:
 - change protobuf field type from int to int64

This should fix increased flakyness in a lot of node e2e tests.
2020-07-17 12:15:43 +03:00
..
balancer Pin go.etcd.io/etcd to 3.4.9 and rebuild vendor 2020-06-12 08:43:10 -07:00
concurrency
credentials
namespace
naming
auth.go
BUILD Pin go.etcd.io/etcd to 3.4.7 and rebuild vendor 2020-04-03 07:15:59 -07:00
client.go Pin go.etcd.io/etcd to 3.4.7 and rebuild vendor 2020-04-03 07:15:59 -07:00
cluster.go
compact_op.go
compare.go
config.go
ctx.go Pin go.etcd.io/etcd to 3.4.7 and rebuild vendor 2020-04-03 07:15:59 -07:00
doc.go
kv.go
lease.go
logger.go
maintenance.go Pin go.etcd.io/etcd to 3.4.9 and rebuild vendor 2020-06-12 08:43:10 -07:00
op.go
options.go
README.md
retry_interceptor.go Pin go.etcd.io/etcd to 3.4.7 and rebuild vendor 2020-04-03 07:15:59 -07:00
retry.go
sort.go
txn.go
utils.go
watch.go go.mod: update etcd to fix e2e tests 2020-07-17 12:15:43 +03:00

etcd/clientv3

Docs Godoc

etcd/clientv3 is the official Go etcd client for v3.

Install

go get go.etcd.io/etcd/clientv3

Get started

Create client using clientv3.New:

cli, err := clientv3.New(clientv3.Config{
	Endpoints:   []string{"localhost:2379", "localhost:22379", "localhost:32379"},
	DialTimeout: 5 * time.Second,
})
if err != nil {
	// handle error!
}
defer cli.Close()

etcd v3 uses gRPC for remote procedure calls. And clientv3 uses grpc-go to connect to etcd. Make sure to close the client after using it. If the client is not closed, the connection will have leaky goroutines. To specify client request timeout, pass context.WithTimeout to APIs:

ctx, cancel := context.WithTimeout(context.Background(), timeout)
resp, err := cli.Put(ctx, "sample_key", "sample_value")
cancel()
if err != nil {
    // handle error!
}
// use the response

For full compatibility, it is recommended to vendor builds using etcd's vendored packages, using tools like golang/dep, as in vendor directories.

Error Handling

etcd client returns 2 types of errors:

  1. context error: canceled or deadline exceeded.
  2. gRPC error: see api/v3rpc/rpctypes.

Here is the example code to handle client errors:

resp, err := cli.Put(ctx, "", "")
if err != nil {
	switch err {
	case context.Canceled:
		log.Fatalf("ctx is canceled by another routine: %v", err)
	case context.DeadlineExceeded:
		log.Fatalf("ctx is attached with a deadline is exceeded: %v", err)
	case rpctypes.ErrEmptyKey:
		log.Fatalf("client-side error: %v", err)
	default:
		log.Fatalf("bad cluster endpoints, which are not etcd servers: %v", err)
	}
}

Metrics

The etcd client optionally exposes RPC metrics through go-grpc-prometheus. See the examples.

Namespacing

The namespace package provides clientv3 interface wrappers to transparently isolate client requests to a user-defined prefix.

Request size limit

Client request size limit is configurable via clientv3.Config.MaxCallSendMsgSize and MaxCallRecvMsgSize in bytes. If none given, client request send limit defaults to 2 MiB including gRPC overhead bytes. And receive limit defaults to math.MaxInt32.

Examples

More code examples can be found at GoDoc.