>
> If that does not give you enough control, then you can set wait_for_ready 
> to false (see here 
> <https://github.com/grpc/grpc/blob/master/doc/wait-for-ready.md>), and 
> implement custom reconnect logic there.

Hi, Eisen,

Not quite understand you here, I know that each RPC will try to connect the 
channel with wait_for_ready woth true. But what I did is I have a channel 
pool that I will get channels from it. So when I get the channel, it may be 
in the TRANS_FAILURE state. I will wait for some time (which is in our own 
retry logic) looking forward the state turns to CONNECTED. But actually 
since it has it own retry logic, sometimes I cannot succeed. That's why I 
want to have my control on issue the channel reconnect.
Is what I am doing not a practical way? May I return OK even when I get the 
TRANS_FAILURE channel?

Thanks,
Yihao
 

在 2017年7月14日星期五 UTC-7上午11:20:28,Noah Eisen写道:
>
> Hi Yihao
>
> We expose the following knobs to configure channel reconnect: 
> INITIAL_BACKOFF, MULTIPLIER, JITTER, MAX_BACKOFF, MIN_CONNECT_TIMEOUT. Most 
> of those can be set via channel args (some , like jitter, have to be hard 
> coded, but a PR to change them to channel args should be trivia). 
>
> If that does not give you enough control, then you can set wait_for_ready 
> to false (see here 
> <https://github.com/grpc/grpc/blob/master/doc/wait-for-ready.md>), and 
> implement custom reconnect logic there.
>
> BEst, 
> Noah
>
> On Fri, Jul 14, 2017 at 11:13 AM, yihao yang <[email protected] 
> <javascript:>> wrote:
>
>> https://github.com/grpc/grpc/blob/master/doc/connection-backoff.md
>>
>> Hi,
>>
>> Can any one talk about why using exponential backoff when reconnecting? 
>> Seems I cannot costume my own reconnect algorithms outside. I can only 
>> recreate a new channel based on some stragety.
>>
>> Thanks,
>> Yihao
>>
>> -- 
>> 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] <javascript:>.
>> To post to this group, send email to [email protected] 
>> <javascript:>.
>> 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/bb814336-6c46-4ab5-ac40-51688d0a2a4a%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/grpc-io/bb814336-6c46-4ab5-ac40-51688d0a2a4a%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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/61789326-f0c4-4e45-807b-3f322b81aa7c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to