Re: [grpc-io] keep channel alive without activity

['Sanjay Pujare' via grpc.io]

Comments inline below:

On Mon, May 16, 2022 at 8:35 AM Rajat Goyal 
wrote:

> Hi Sanjay / Grpc team,
>
> I have implemented RPC based regular pings. Like I am sending some
> dummy request each minute to LB once connected from client side.
> I observed below :
> a) This method works fine if there is no request from the server side.
> This way the connection is alive for many hours without issues.
>

"request from the server side": just want to clarify what is being said.
You mean a response message since a server can only send response messages
back. Or did you mean server sending requests on a different connection to
another server?



> b) But this method doesn't work if there is some bi-directional
> request from the server. The moment it receives a response from server, the
> connections is dropped from LB after exactly 5 mins, even if I am sending a
> regular dummy request from the client side every minute.
>

Again I would like to clarify your "bi-directional request from the server"
: do you mean a bi-di RPC into the server where server is sending responses
to the client? And in such a case the LB drops the connection after 5 mins?


>
> I also checked the server logs the dummy request is being received every
> min, which means client is sending regular 1 min ping, but still LB is
> dropping the connection.
> While in case there is no response from server side, the connection is not
> dropped by LB.
>
> Can you please help me what grpc / LB might be doing in both cases ?
>

To summarize my understanding of what you are. saying: when a connection is
established through the ALB to a gRPC backend the connection stays alive
indefinitely if the client only sends a dummy RPC every minute. This dummy
RPC has a dummy request but no response (only header(s) and status code).
As soon as you send any real RPCs where the server sends any response
messages then the LB does not keep the connection alive but drops it 5
minutes after the last non-dummy RPC. Is this correct?



>
> Regards,
> Rajat
>
>
> On Tue, Jan 11, 2022 at 4:01 AM Sanjay Pujare 
> wrote:
>
>> Check this
>> https://stackoverflow.com/questions/66818645/http2-ping-frames-over-aws-alb-grpc-keepalive-ping
>>
>> "*ALB does not support the HTTP2 ping frames*."
>>
>> On Mon, Jan 10, 2022 at 12:16 PM Rajat Goyal 
>> wrote:
>>
>>> ALB is configured with idle-timeout - 5 minutes.
>>> I configured bi-di client with :
>>>  keepAliveWithoutCalls(true).keepAliveTime(90,
>>> TimeUnit.SECONDS).keepAliveTimeout(10, TimeUnit.SECONDS)
>>> while server is configured with :
>>> permitKeepAliveWithoutCalls(true).permitKeepAliveTime(1, TimeUnit.MINUTES)
>>>
>>> But I received INTERNAL: HTTP/2 error code: PROTOCOL_ERROR Received Rst
>>> Stream after exactly 5 minutes. Which looks like ALB has dropped the
>>> connection after 5 minutes.
>>>
>>> Any idea how we can keep idle connection alive ?
>>>
>>>
>>>
>>> On Mon, Jan 10, 2022 at 10:39 PM Rajat Goyal 
>>> wrote:
>>>
 Hi Sanjay,

  I see that bi-directional streamObserver object gets call back
 onError() in case of any error in network.

 Isn't that done by any heartbeat mechanism already?. If so, then
 connection at ALB should be active with these ping-pong packets ?

 Regards,
 Rajat

 On Mon, 10 Jan, 2022, 10:33 pm Sanjay Pujare, 
 wrote:

> This may probably help?
> https://grpc.io/blog/grpc-on-http2/#keeping-connections-alive ?
>
> On Mon, Jan 10, 2022 at 8:54 AM Rajat Goyal <
> rajatgoyal247...@gmail.com> wrote:
>
>> Hi,
>>
>>   Gentle reminder for any resolution for above.
>>
>> Regards,
>> Rajat
>>
>> On Sun, 9 Jan, 2022, 6:50 pm Rajat Goyal, 
>> wrote:
>>
>>> Hi,
>>>
>>>  We have a system where clients open bi-directional grpc stream
>>> to ALB, which proxies to one of active server. So
>>>
>>>  bi-di
>>> client <>  ALB  <> server
>>>
>>> In-case of any failure of connection, clients re-connects to us as
>>> we want to keep a bi-di channel open.
>>>
>>> Question is : How can we keep the channel open even if there is no
>>> activity for sometime. ALB are configured with 300 sec idle-timeout 
>>> which
>>> means it will drop the connection if no packets are exchanged in 300 
>>> sec.
>>>
>>> As we want to keep the connection open as much possible ( only
>>> re-create in-case of any issue),  and not let it die due to idle 
>>> timeout,
>>> what properties should server can client set ?
>>> Should keep-alive setting at both client & server help out ?
>>>
>>>
>>> --
>>> 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.

[grpc-io] Protoc does not export grpc-web files [MacOS]

[Antonello Palazzi]

I have a simple proto file:
syntax = "proto3";

package SettingsSvc;
service Settings {
  rpc FetchSettings(SettingsRequest) returns (SettingsResponse) {}
}

message SettingsRequest { 
  string language = 1;
}

message SettingsResponse {
  string cvTooltip = 1;
  string themeTooltip = 2;
  string githubLocation = 3;
  string gitlabLocation = 4;
  string linkedinLocation = 5;
  string name = 6;
  int32 year = 7;
} 

I am trying to generate the files for a react (TS template) web client. As 
suggested by the official grpc-web page 
 I am running the 
protoc command as follows:
protoc -I=. settings.proto --js_out=import_style=commonjs,binary:. 
--grpc-web_out=import_style=typescript,mode=grpcweb:. 

However, the only file I get is "settings_pb.js", which is the one 
generated by the "--js_out" instruction. The file that should be generated 
by the "--grpc-web_out" instruction (SettingsClientPb.ts) is missing.

I tried using "import_style=commonjs" and "import_style=commonjs+dts" as 
well, but no luck. The command returns no errors but it does not produce 
the expected output files.

I installed protoc with brew and I am using version 1.3.1 of the grpc-web 
code generator plugin .

Can someone help?

Thanks.

Antonello

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/88256c8f-70a4-4f62-8e3e-1b1210741d40n%40googlegroups.com.

[grpc-io] Method/option to limit # of subchannels created?

['Peter Hurley' via grpc.io]

Hi,

Is there a method or option to limit the number of subchannels created to 
be fewer than the number of addresses resolved by ares?

Is there anything in the execution chain: ares resolver -> server address 
list -> address sorting -> subchannel list creation that can ultimately 
reduce the # of subchannels created?

Regards,
Peter Hurley

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/44973427-6706-4b0b-bbd6-9f8179b81312n%40googlegroups.com.

Re: [grpc-io] keep channel alive without activity

[Rajat Goyal]

Hi Sanjay / Grpc team,

I have implemented RPC based regular pings. Like I am sending some
dummy request each minute to LB once connected from client side.
I observed below :
a) This method works fine if there is no request from the server side.
This way the connection is alive for many hours without issues.
b) But this method doesn't work if there is some bi-directional request
from the server. The moment it receives a response from server, the
connections is dropped from LB after exactly 5 mins, even if I am sending a
regular dummy request from the client side every minute.

I also checked the server logs the dummy request is being received every
min, which means client is sending regular 1 min ping, but still LB is
dropping the connection.
While in case there is no response from server side, the connection is not
dropped by LB.

Can you please help me what grpc / LB might be doing in both cases ?

Regards,
Rajat


On Tue, Jan 11, 2022 at 4:01 AM Sanjay Pujare 
wrote:

> Check this
> https://stackoverflow.com/questions/66818645/http2-ping-frames-over-aws-alb-grpc-keepalive-ping
>
> "*ALB does not support the HTTP2 ping frames*."
>
> On Mon, Jan 10, 2022 at 12:16 PM Rajat Goyal 
> wrote:
>
>> ALB is configured with idle-timeout - 5 minutes.
>> I configured bi-di client with :
>>  keepAliveWithoutCalls(true).keepAliveTime(90,
>> TimeUnit.SECONDS).keepAliveTimeout(10, TimeUnit.SECONDS)
>> while server is configured with :
>> permitKeepAliveWithoutCalls(true).permitKeepAliveTime(1, TimeUnit.MINUTES)
>>
>> But I received INTERNAL: HTTP/2 error code: PROTOCOL_ERROR Received Rst
>> Stream after exactly 5 minutes. Which looks like ALB has dropped the
>> connection after 5 minutes.
>>
>> Any idea how we can keep idle connection alive ?
>>
>>
>>
>> On Mon, Jan 10, 2022 at 10:39 PM Rajat Goyal 
>> wrote:
>>
>>> Hi Sanjay,
>>>
>>>  I see that bi-directional streamObserver object gets call back
>>> onError() in case of any error in network.
>>>
>>> Isn't that done by any heartbeat mechanism already?. If so, then
>>> connection at ALB should be active with these ping-pong packets ?
>>>
>>> Regards,
>>> Rajat
>>>
>>> On Mon, 10 Jan, 2022, 10:33 pm Sanjay Pujare, 
>>> wrote:
>>>
 This may probably help?
 https://grpc.io/blog/grpc-on-http2/#keeping-connections-alive ?

 On Mon, Jan 10, 2022 at 8:54 AM Rajat Goyal 
 wrote:

> Hi,
>
>   Gentle reminder for any resolution for above.
>
> Regards,
> Rajat
>
> On Sun, 9 Jan, 2022, 6:50 pm Rajat Goyal, 
> wrote:
>
>> Hi,
>>
>>  We have a system where clients open bi-directional grpc stream
>> to ALB, which proxies to one of active server. So
>>
>>  bi-di
>> client <>  ALB  <> server
>>
>> In-case of any failure of connection, clients re-connects to us as we
>> want to keep a bi-di channel open.
>>
>> Question is : How can we keep the channel open even if there is no
>> activity for sometime. ALB are configured with 300 sec idle-timeout which
>> means it will drop the connection if no packets are exchanged in 300 sec.
>>
>> As we want to keep the connection open as much possible ( only
>> re-create in-case of any issue),  and not let it die due to idle timeout,
>> what properties should server can client set ?
>> Should keep-alive setting at both client & server help out ?
>>
>>
>> --
>> 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 view this discussion on the web visit
>> https://groups.google.com/d/msgid/grpc-io/532f5551-e978-467e-b71c-0031a54953bfn%40googlegroups.com
>> 
>> .
>>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/grpc-io/CALO6TtuVMUxHQmZMGj1wvD7r4qvRQuKd2gy0j%2B0z8b8EYdw7BA%40mail.gmail.com
> 
> .
>


-- 
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 view this discussion on the web visit 

[grpc-io] Grpc server with async and sync services at the same time

[Adrian Tut]

I need to be able to serve responses for some particular requests from the 
main thread, while the rest can arrive from any thread. With that in mind, 
I created a GRPC server which has 2 services, one is implemented as an 
AsyncService, and the other as a sync service.

However, when adding a completion queue, the sync service *no longer 
responds to requests.*

Is that not supported and if so, what alternatives are there?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/913e2c47-55b1-48f9-a829-a9f6a47a0098n%40googlegroups.com.