Just a follow-up to say I got an answer to this question from Eric Anderson here: https://stackoverflow.com/questions/46570634/can-a-grpc-client-connect-timeout-be-set-independent-of-reconnect-backoff-settin
Summary: it's a bug in grpc, and there's work underway to fix it: https://github.com/grpc/grpc/pull/13121 -- 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 [email protected]. To post to this group, send email to [email protected]. 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/8f378432-2662-4694-b7da-511ed1b961ed%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
