I created a PR for this:
https://github.com/grpc/grpc/pull/28506
Op donderdag 6 januari 2022 om 15:02:11 UTC+1 schreef John Forensics:
> Still getting closed:
>
> On windows gRPC is handled using WSASend asynchronous IO. When reaching a
> TCP congested situation WSASend should report *WSAEWOU
Im interesting to start to create a project for integrate grpc to deno like
a third party module for deno, im interesting to know the framework with
witch language already is supported today with node.js, cuz i suppose the
integration will be like right now is with node.js
--
You received this
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 :
>
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
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
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,
>>
>>
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
>
