Retry policy

[ili...@luminatewireless.com]

Hi there,

We are in the process of upgrading gRPC from git commit ID c7767bb1244204724c72422c11b8c6a146caef39 (March 2016) to git commit ID 4fe0d977ed1d04cbee6b44d6f30e56e5133287b5 (February 2017).

One new behaviour we have observed is, if the client fails to connect to the server, it seems to take longer for the retries to happen. Has the retry policy changed? Previously, once the server was available, the client channel would connect within one or two seconds. Now, it seems to take closer to 10 seconds once the server is available.

Ilina

[Stanley Cheung]

What language are your server and client implemented in respectively?

[Yang Gao]

Ilina

You may want to test by setting channel_arg with key grpc.testing.fixed_reconnect_backoff_ms to a smaller value to see whether it works. Or maybe playing with the values in client_channel/subchannel.c. I do not think we have a arg for the min_backoff right now though.

--
You received this message because you are subscribed to the Google Groups "grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+unsubscribe@googlegroups.com.
To post to this group, send email to grp...@googlegroups.com.
Visit this group at https://groups.google.com/group/grpc-io.
To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/6b24eaf4-93ff-47c3-a8de-1594f6693173%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Ilina Mitra]

Server is in Java and client is in C++