Oh, sorry. I wasn't paying attention enough to the screenshot. Those are TCP keepalives. Most discussion about keepalives in gRPC involves using HTTP/2 pings.
The netty server enables SO_KEEPALIVE, but leaves the settings at their defaults. In most cases the defaults are to send a TCP keepalive after 2 hours of inactivity. The server OS must be configured to use 1s keepalives by default, which seems very aggressive. On Thu, Jan 10, 2019 at 5:41 PM <[email protected]> wrote: > 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 <[email protected]> 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 [email protected]. >>> To post to this group, send email to [email protected]. >>> 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 >>> <https://groups.google.com/d/msgid/grpc-io/b6cca740-92f2-47b8-9c8b-d0bbadd825b1%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> 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 [email protected]. > To post to this group, send email to [email protected]. > 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 > <https://groups.google.com/d/msgid/grpc-io/2a30061d-bb97-43f9-9408-6ea35d4251e9%40googlegroups.com?utm_medium=email&utm_source=footer> > . > 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 [email protected]. To post to this group, send email to [email protected]. 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%2B4M1oNDHROeYqh-s9S%3DG5ouAFwnUx%3DiueGyamt9YfZQM%3DFhow%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
smime.p7s
Description: S/MIME Cryptographic Signature
