Re: [grpc-io] enable client side keepalive but seeing server side initiate the ping

2019-01-10 Thread eleanore . jin
Hi Eric, 

Thanks for the reply, but I only enabled ping on client side, and only 
configured server to allow client sending pings, but the server is not 
configured to send pings.

On Thursday, January 10, 2019 at 5:07:09 PM UTC-8, Eric Anderson wrote:
>
> The client sends a keepalive ping after X time since the last read. The 
> server does similar. If the client receives the server's ping before it 
> does its own keepalive ping, that resets the "time since last read" timer; 
> the server's keepalive is enough for the client to know the connection is 
> still good.
>
> On Mon, Jan 7, 2019 at 4:56 PM > wrote:
>
>>
>> Hi, 
>>
>> I have enabled client side keepalive and also on the server side, enable 
>> permission to send ping via NettyServerBuilder.permitKeepAliveTime(), 
>>
>> however, what I see from the wireshark, the keepalive ping seems to be 
>> initiated from server side (gRPC server listens on 9096): 
>>
>> [image: Screen Shot 2019-01-07 at 4.29.01 PM.png]
>>
>>
>> Any ideas why this happens ?
>>
>> Thanks a lot!
>>
>> -- 
>> 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/b6cca740-92f2-47b8-9c8b-d0bbadd825b1%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/2a30061d-bb97-43f9-9408-6ea35d4251e9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [grpc-io] Re: [grpc-java] global exception handler on client-side

2019-01-10 Thread 'Kun Zhang' via grpc.io
Yes it's public API and we guarantee it won't break within the same major 
version.

On Thursday, January 10, 2019 at 12:13:52 AM UTC-8, eval...@exadel.com 
wrote:
>
> Is ClientCalls class part of public API? I.e. am I safe to assume that it 
> won't have breaking changes as long as I'm using grpc 1.X?
>

-- 
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/a54fed0e-84c6-4de5-a99e-1bd3c76ff1d8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[grpc-io] Re: gRPC java (1.16) RoundRobinLoadBalancer is not able to load balancing to the newly added server

2019-01-10 Thread 'Kun Zhang' via grpc.io
SubChannel getting created for the new server means round-robin is aware of 
this new server and tries to connect.
The creation log starts with the logId of the Subchannel. Do you see any 
other logs related to that logId?
My suspicion is that the Subchannel couldn't get connected.

On Thursday, January 10, 2019 at 4:34:58 PM UTC-8, eleano...@gmail.com 
wrote:
>
> Hi Kun, 
>
> Thanks for your reply, I did see that new SubChannel gets created for the 
> new server,  do you mean that so long as the new server's subchannel gets 
> created, it should take effect immediately, meaning the new server should 
> also get the traffic?
>
> Thanks a lot!
>
> On Thursday, January 10, 2019 at 4:00:28 PM UTC-8, Kun Zhang wrote:
>>
>> Can you find logs from InternalSubchannel that mention the new server?
>> If the new server can not be connected, round-robin won't use it.
>>
>> On Wednesday, January 9, 2019 at 10:18:47 AM UTC-8, eleano...@gmail.com 
>> wrote:
>>>
>>> Hi, 
>>>
>>> in my java gRPC client, when I create the ManagedChannel, I am passing 
>>> my custom NameResolver, and using RoundRobinLoadBalancer. When my 
>>> NameResolver is notified with a change to the server list (new server 
>>> added), it will call Listener.onAddress and pass the updated the list.
>>>
>>> I see from the Log: the onAddress is called from 
>>> NameResolverListenerImpl, (9097 is the new server address added)
>>>
>>> resolved address: [[addrs=[localhost/127.0.0.1:9096], attrs={}], 
>>> [addrs=[localhost/127.0.0.1:9097], attrs={}]], config={}
>>>
>>>
>>> however, the traffic is not coming to the new server, did I miss 
>>> anything?
>>>
>>>
>>> Thanks a lot!
>>>
>>>
>>>
>>>
>>>
>>>

-- 
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/2929af22-83c9-4a34-91c4-49c45cc9f9e5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [grpc-io] enable client side keepalive but seeing server side initiate the ping

2019-01-10 Thread 'Eric Anderson' via grpc.io
The client sends a keepalive ping after X time since the last read. The
server does similar. If the client receives the server's ping before it
does its own keepalive ping, that resets the "time since last read" timer;
the server's keepalive is enough for the client to know the connection is
still good.

On Mon, Jan 7, 2019 at 4:56 PM  wrote:

>
> Hi,
>
> I have enabled client side keepalive and also on the server side, enable
> permission to send ping via NettyServerBuilder.permitKeepAliveTime(),
>
> however, what I see from the wireshark, the keepalive ping seems to be
> initiated from server side (gRPC server listens on 9096):
>
> [image: Screen Shot 2019-01-07 at 4.29.01 PM.png]
>
>
> Any ideas why this happens ?
>
> Thanks a lot!
>
> --
> 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/b6cca740-92f2-47b8-9c8b-d0bbadd825b1%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%2B4M1oNT%2Bs-1fsK-2sMLORzFtgHWGCbb9j1mk%2B9NviVw5yWAXg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


smime.p7s
Description: S/MIME Cryptographic Signature


[grpc-io] Re: gRPC java (1.16) RoundRobinLoadBalancer is not able to load balancing to the newly added server

2019-01-10 Thread eleanore . jin
Hi Kun, 

Thanks for your reply, I did see that new SubChannel gets created for the 
new server,  do you mean that so long as the new server's subchannel gets 
created, it should take effect immediately, meaning the new server should 
also get the traffic?

Thanks a lot!

On Thursday, January 10, 2019 at 4:00:28 PM UTC-8, Kun Zhang wrote:
>
> Can you find logs from InternalSubchannel that mention the new server?
> If the new server can not be connected, round-robin won't use it.
>
> On Wednesday, January 9, 2019 at 10:18:47 AM UTC-8, eleano...@gmail.com 
> wrote:
>>
>> Hi, 
>>
>> in my java gRPC client, when I create the ManagedChannel, I am passing my 
>> custom NameResolver, and using RoundRobinLoadBalancer. When my NameResolver 
>> is notified with a change to the server list (new server added), it will 
>> call Listener.onAddress and pass the updated the list.
>>
>> I see from the Log: the onAddress is called from 
>> NameResolverListenerImpl, (9097 is the new server address added)
>>
>> resolved address: [[addrs=[localhost/127.0.0.1:9096], attrs={}], 
>> [addrs=[localhost/127.0.0.1:9097], attrs={}]], config={}
>>
>>
>> however, the traffic is not coming to the new server, did I miss anything?
>>
>>
>> Thanks a lot!
>>
>>
>>
>>
>>
>>

-- 
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/a705d4f7-428e-4891-a015-cabbe2d4de90%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[grpc-io] Re: gRPC java (1.16) RoundRobinLoadBalancer is not able to load balancing to the newly added server

2019-01-10 Thread 'Kun Zhang' via grpc.io
Can you find logs from InternalSubchannel that mention the new server?
If the new server can not be connected, round-robin won't use it.

On Wednesday, January 9, 2019 at 10:18:47 AM UTC-8, eleano...@gmail.com 
wrote:
>
> Hi, 
>
> in my java gRPC client, when I create the ManagedChannel, I am passing my 
> custom NameResolver, and using RoundRobinLoadBalancer. When my NameResolver 
> is notified with a change to the server list (new server added), it will 
> call Listener.onAddress and pass the updated the list.
>
> I see from the Log: the onAddress is called from NameResolverListenerImpl, 
> (9097 is the new server address added)
>
> resolved address: [[addrs=[localhost/127.0.0.1:9096], attrs={}], 
> [addrs=[localhost/127.0.0.1:9097], attrs={}]], config={}
>
>
> however, the traffic is not coming to the new server, did I miss anything?
>
>
> Thanks a lot!
>
>
>
>
>
>

-- 
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/d136492a-bba3-451b-b1fe-87ed9c01d715%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [grpc-io] Re: [grpc-java] global exception handler on client-side

2019-01-10 Thread evaliauka via grpc.io
Is ClientCalls class part of public API? I.e. am I safe to assume that it 
won't have breaking changes as long as I'm using grpc 1.X?

-- 


CONFIDENTIALITY
NOTICE: This email and files attached to it are 
confidential. If you
are not the intended recipient you are hereby notified 
that using,
copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited. If you have
received 
this email in error please notify the sender and delete this
email.

-- 
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/20d55688-d8e6-4d06-adaa-9d71ee128aba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.