Seems to me that there should be an autoback off. Server warning don't
call back again for 4 min . Well behaved clients follow that, bad ones get
disconnected.
On Monday, June 5, 2017 at 7:17:30 PM UTC-4, Eric Anderson wrote:
>
> In 1.3 we started allowing clients to be more aggressive. From
Thanks makes sense. I was setting this to 1 sec at one time :) ... not
production but just *playing* around and I think it was working without a
hitch. However I think they upgraded the server grpc and now im getting
this. If this is all that's going on no worries then. Like I said oddly
wi
In 1.3 we started allowing clients to be more aggressive. From the 1.3
release notes:
"Keepalives in Netty and OkHttp now allow sending pings without outstanding
RPCs. The minimum keepalive time was also reduced from 1 minute to 10
seconds. Clients must get permission from the services they use be
Hi
I set on a grpc stream with NettyChannel options:
keepAliveTime"(60L, TimeUnit.SECONDS});
keepAliveTimeout{8L, TimeUnit.SECONDS});
At times in the code I've added sleep for 15 min. I see on Wireshark the
keep alives.
But after a time I see :
---
It looks like we're going to be pursuing a different approach for this, in
which the header field is set in the VTK layer based on static
configuration. As a result, I am withdrawing this gRFC.
Abhishek is driving forward the VTK proposal, so I presume that he will
publish something once there ar
