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

2017-04-26 Thread 'Eric Anderson' via grpc.io 
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 attempt takes 100 ms, then the next attempt
would happen 900 ms later. If the initial attempt takes 20 seconds, then
the next attempt would happen immediately.

On Tue, Apr 25, 2017 at 5:34 PM, ncteisen via grpc.io <
grpc-io@googlegroups.com> wrote:

> 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:
> - GRPC_ARG_MIN_RECONNECT_BACKOFF_MS
> - GRPC_ARG_MAX_RECONNECT_BACKOFF_MS
> - GRPC_ARG_INITIAL_RECONNECT_BACKOFF_MS
>
> Setting those to lower number should cause the reconnection to happen
> faster.
>
> On Friday, April 21, 2017 at 1:29:01 PM UTC-7, Yaz Saito wrote:
>>
>> 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 <
>> grp...@googlegroups.com> wrote:
>>
>>> 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. Basically, we're willing to wait 20 seconds for DNS, TCP,
>>> TLS, and similar to complete. If they fail though, then there may be a
>>> delay until the next attempt.
>>>
>>> On Tue, Apr 18, 2017 at 3:54 PM, 'Penn (Dapeng) Zhang' via grpc.io <
>>> grp...@googlegroups.com> wrote:
>>>
 In what language? There are (at least) two kinds of reties: connection
 attempt retry, and high level RPC call retry. I assume your question is
 about the former.

 On Friday, April 14, 2017 at 12:25:11 PM UTC-7, Yaz Saito wrote:
>
> I'm trying out 1.2.4 (I was using 1.0.1), and I noticed that the
> channel connection retry policy has changed. Looks like the newest code
> retries connection at intervals of 1s, 20s, 32s, 51.2s, etc. And I'm not
> happy with the huge jump from 1s to 20s. This means when I start a server
> then try to connect to it (which happens in unittests often), I often wait
> for 20s. Am I understanding the code right, and is there a way to force 
> the
> channel to reconnect more quickly?
>
> --
> yaz
>
 --
 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+u...@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/ms
 gid/grpc-io/a4b82f09-4eb7-4e6b-aabd-71198e38b558%40googlegroups.com
 
 .

 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 grpc-io+u...@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/ms
>>> gid/grpc-io/CA%2B4M1oPAgg2XRCLbkmVG5KE%3DSmaARVevxwn_
>>> gfu40HQGMqj4Sg%40mail.gmail.com
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> yaz
>>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to grpc-io@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/8d03fd13-df76-4f16-9e5d-fb864df24519%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You

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

2017-04-25 Thread ncteisen via grpc.io 
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:
- GRPC_ARG_MIN_RECONNECT_BACKOFF_MS
- GRPC_ARG_MAX_RECONNECT_BACKOFF_MS
- GRPC_ARG_INITIAL_RECONNECT_BACKOFF_MS

Setting those to lower number should cause the reconnection to happen 
faster.

On Friday, April 21, 2017 at 1:29:01 PM UTC-7, Yaz Saito wrote:
>
> 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 <
> grp...@googlegroups.com > wrote:
>
>> 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. Basically, we're willing to wait 20 seconds for DNS, TCP, 
>> TLS, and similar to complete. If they fail though, then there may be a 
>> delay until the next attempt.
>>
>> On Tue, Apr 18, 2017 at 3:54 PM, 'Penn (Dapeng) Zhang' via grpc.io <
>> grp...@googlegroups.com > wrote:
>>
>>> In what language? There are (at least) two kinds of reties: connection 
>>> attempt retry, and high level RPC call retry. I assume your question is 
>>> about the former.
>>>
>>> On Friday, April 14, 2017 at 12:25:11 PM UTC-7, Yaz Saito wrote:

 I'm trying out 1.2.4 (I was using 1.0.1), and I noticed that the 
 channel connection retry policy has changed. Looks like the newest code 
 retries connection at intervals of 1s, 20s, 32s, 51.2s, etc. And I'm not 
 happy with the huge jump from 1s to 20s. This means when I start a server 
 then try to connect to it (which happens in unittests often), I often wait 
 for 20s. Am I understanding the code right, and is there a way to force 
 the 
 channel to reconnect more quickly?

 -- 
 yaz

>>> -- 
>>> 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+u...@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/a4b82f09-4eb7-4e6b-aabd-71198e38b558%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>> 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 grpc-io+u...@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/CA%2B4M1oPAgg2XRCLbkmVG5KE%3DSmaARVevxwn_gfu40HQGMqj4Sg%40mail.gmail.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> yaz
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to grpc-io@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/8d03fd13-df76-4f16-9e5d-fb864df24519%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

2017-04-21 Thread Yaz Saito 
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?
>
> 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. Basically, we're willing to wait 20 seconds for DNS, TCP,
> TLS, and similar to complete. If they fail though, then there may be a
> delay until the next attempt.
>
> On Tue, Apr 18, 2017 at 3:54 PM, 'Penn (Dapeng) Zhang' via grpc.io <
> grpc-io@googlegroups.com> wrote:
>
>> In what language? There are (at least) two kinds of reties: connection
>> attempt retry, and high level RPC call retry. I assume your question is
>> about the former.
>>
>> On Friday, April 14, 2017 at 12:25:11 PM UTC-7, Yaz Saito wrote:
>>>
>>> I'm trying out 1.2.4 (I was using 1.0.1), and I noticed that the channel
>>> connection retry policy has changed. Looks like the newest code retries
>>> connection at intervals of 1s, 20s, 32s, 51.2s, etc. And I'm not happy with
>>> the huge jump from 1s to 20s. This means when I start a server then try to
>>> connect to it (which happens in unittests often), I often wait for 20s. Am
>>> I understanding the code right, and is there a way to force the channel to
>>> reconnect more quickly?
>>>
>>> --
>>> yaz
>>>
>> --
>> 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+unsubscr...@googlegroups.com.
>> To post to this group, send email to grpc-io@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/ms
>> gid/grpc-io/a4b82f09-4eb7-4e6b-aabd-71198e38b558%40googlegroups.com
>> 
>> .
>>
>> 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 grpc-io+unsubscr...@googlegroups.com.
> To post to this group, send email to grpc-io@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/CA%2B4M1oPAgg2XRCLbkmVG5KE%3DSmaARVevxwn_gfu40HQGMqj4Sg%
> 40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
yaz

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to grpc-io@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/CALsnwn%2B%2Bw5FDQPGERW-Q5Q5pFXw%3DAyVGGB9YK%3DXOnC_Rce6aoA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

2017-04-18 Thread 'Eric Anderson' via grpc.io 
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. Basically, we're willing to wait 20 seconds for DNS, TCP,
TLS, and similar to complete. If they fail though, then there may be a
delay until the next attempt.

On Tue, Apr 18, 2017 at 3:54 PM, 'Penn (Dapeng) Zhang' via grpc.io <
grpc-io@googlegroups.com> wrote:

> In what language? There are (at least) two kinds of reties: connection
> attempt retry, and high level RPC call retry. I assume your question is
> about the former.
>
> On Friday, April 14, 2017 at 12:25:11 PM UTC-7, Yaz Saito wrote:
>>
>> I'm trying out 1.2.4 (I was using 1.0.1), and I noticed that the channel
>> connection retry policy has changed. Looks like the newest code retries
>> connection at intervals of 1s, 20s, 32s, 51.2s, etc. And I'm not happy with
>> the huge jump from 1s to 20s. This means when I start a server then try to
>> connect to it (which happens in unittests often), I often wait for 20s. Am
>> I understanding the code right, and is there a way to force the channel to
>> reconnect more quickly?
>>
>> --
>> yaz
>>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to grpc-io@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/a4b82f09-4eb7-4e6b-aabd-71198e38b558%40googlegroups.com
> 
> .
>
> 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 grpc-io+unsubscr...@googlegroups.com.
To post to this group, send email to grpc-io@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/CA%2B4M1oPAgg2XRCLbkmVG5KE%3DSmaARVevxwn_gfu40HQGMqj4Sg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


smime.p7s
Description: S/MIME Cryptographic Signature