|
@@ -102,6 +102,12 @@ To recover from the low space quota alarm:
|
|
|
2. [Defragment][maintenance-defragment] every etcd endpoint.
|
|
2. [Defragment][maintenance-defragment] every etcd endpoint.
|
|
|
3. [Disarm][maintenance-disarm] the alarm.
|
|
3. [Disarm][maintenance-disarm] the alarm.
|
|
|
|
|
|
|
|
|
|
+### What does the etcd warning "etcdserver/api/v3rpc: transport: http2Server.HandleStreams failed to read frame: read tcp 127.0.0.1:2379->127.0.0.1:43020: read: connection reset by peer" mean?
|
|
|
|
|
+
|
|
|
|
|
+This is gRPC-side warning when a server receives a TCP RST flag with client-side streams being prematurely closed. For example, a client closes its connection, while gRPC server has not yet processed all HTTP/2 frames in the TCP queue. Some data may have been lost in server side, but it is ok so long as client connection has already been closed.
|
|
|
|
|
+
|
|
|
|
|
+Only [old versions of gRPC](https://github.com/grpc/grpc-go/issues/1362) log this. etcd [>=v3.2.13 by default log this with DEBUG level](https://github.com/coreos/etcd/pull/9080), thus only visible with `--debug` flag enabled.
|
|
|
|
|
+
|
|
|
## Performance
|
|
## Performance
|
|
|
|
|
|
|
|
### How should I benchmark etcd?
|
|
### How should I benchmark etcd?
|
Gyuho Lee