tree a2ed693964ce8730c61329e1e67272ba5ce30625
parent b28608a9dbfcc585a10c13222c50cfeb50b7ac7a
author Krzysztof Dryś <krzysztofdrys@users.noreply.github.com> 1529445280 +0200
committer Menghan Li <menghanl@google.com> 1529445280 -0700

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.