So it seems like I'm getting hit with the problem addressed in
https://github.com/grpc/grpc-java/pull/5599 and
https://github.com/grpc/proposal/blob/master/A18-tcp-user-timeout.md. It
exactly matches the 15min it takes to reset, the write heavy workload and
the default linux TCP timeout.
I'm
You'll need to read the docs of that method I linked (and the other ones
with "keepalive" in the name). It discusses what will happen with regards
to active calls.
On Wednesday, June 5, 2019 at 11:02:34 AM UTC-7, yfe...@gmail.com wrote:
>
> Hey Carl,
>
> Thanks for your help with this!
>
> Is
Hey Carl,
Thanks for your help with this!
Is it correct that if I am submitting calls every 10 seconds, but my
keepAliveTime > 10seconds, then no keep alives would be sent? Or are keep
alives sent regardless of request activity?
Is it only failed keep alive pings that will indicate a channel
Try setting the keep alive settings defined here:
https://grpc.github.io/grpc-java/javadoc/io/grpc/ManagedChannelBuilder.html#keepAliveTimeout-long-java.util.concurrent.TimeUnit-
On Wednesday, June 5, 2019 at 10:48:38 AM UTC-7, yfe...@gmail.com wrote:
>
> Hey folks,
>
> I'm making calls using a
