grpc-go/balancer
Krzysztof Dryś 536e74e045 Don't log grpclb server ending connection as error (#2162)
Fixes https://github.com/grpc/grpc-go/issues/2161

I introduced `serverTerminatedConnectionErr `, because I wanted `callRemoteBalancer` to still returns error on a terminated connections. Its client, which is function `watchRemoteBalancer` can decide how to log this error.

When remote grpclb-server terminates the connection, don't log it as
error. Instead, log it as info.

It is natural for servers to terminate long lived grpc streaming
connections. Two sample reasons to do this are: load balancing and
deployment of a new version. Therefore client of grpclb-server shouldn't
recognise this situation as an error.
2018-06-19 14:54:40 -07:00
..
base Remove redundant return statements (gosimple) 2018-04-15 12:43:34 +02:00
grpclb Don't log grpclb server ending connection as error (#2162) 2018-06-19 14:54:40 -07:00
roundrobin internal: move leakcheck to internal/ (#2129) 2018-06-07 16:57:56 -07:00
balancer.go Split grpclb out of top level grpc package (#2107) 2018-06-05 09:54:12 -07:00