Re: [grpc-io] Re: connection retry policy in 1.2

That behavior is the opposite of the spec . The initial backoff occurs during the 1 second after the connection attempt *started*, but the initial attempt should be given up to 20 seconds before it times out. If the initial

Re: [grpc-io] Re: connection retry policy in 1.2

The behavior you are seeing is correct, the default values being used can be found at https://github.com/grpc/grpc/blob/master/src/core/ext/filters/client_channel/subchannel.c#L62. If you would like to override the default behavior, you can use three channel args: -

Re: [grpc-io] Re: connection retry policy in 1.2

The client and servers are C++, and I'm talking about the connection retry, not an RPC retry. Also, the server is on a UNIX socket (unix:/path). On Tue, Apr 18, 2017 at 4:01 PM, 'Eric Anderson' via grpc.io < grpc-io@googlegroups.com> wrote: > Also, how did you get those reconnect attempt times?

Re: [grpc-io] Re: connection retry policy in 1.2

Also, how did you get those reconnect attempt times? All languages should be following our standard connection backoff algorithm . If one's not, that would be a bug. Note that 20s is permitted as a minimum connect time.