Christian Schwarz ab3e783168 rpc: treat protocol handshake errors as permanent ...

treat handshake errors as permanent on the client

The issue was observed by 100% CPU usage due to lack ofrate-limiting in
dataconn.ReqPing retries=> safeguard that

2019-03-15 16:18:01 +01:00

..

dataconn

replication/driver: automatic retries on connectivity-related errors

2019-03-13 15:00:40 +01:00

grpcclientidentity

rpc/ctrl: nicer perr info debug log messages

2019-03-13 19:20:04 +01:00

netadaptor

rpc rewrite: control RPCs using gRPC + separate RPC for data transfer

2019-03-13 13:53:48 +01:00

transportmux

rpc: treat protocol handshake errors as permanent

2019-03-15 16:18:01 +01:00

versionhandshake

rpc: treat protocol handshake errors as permanent

2019-03-15 16:18:01 +01:00

rpc_client.go

rpc: treat protocol handshake errors as permanent

2019-03-15 16:18:01 +01:00

rpc_debug.go

rpc rewrite: control RPCs using gRPC + separate RPC for data transfer

2019-03-13 13:53:48 +01:00

rpc_doc.go

rpc rewrite: control RPCs using gRPC + separate RPC for data transfer

2019-03-13 13:53:48 +01:00

rpc_logging.go

rpc rewrite: control RPCs using gRPC + separate RPC for data transfer

2019-03-13 13:53:48 +01:00

rpc_mux.go

rpc rewrite: control RPCs using gRPC + separate RPC for data transfer

2019-03-13 13:53:48 +01:00

rpc_server.go

replication: refactor driving logic (no more explicit state machine)

2019-03-13 15:00:40 +01:00