Replies: 1 comment 1 reply
-
Hey @szajbus - Thanks for your question. Can you please confirm the full config you are using for etcd server and any other info that will help us recreate your scenario easily. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I am using a client that sends pings to etcd server periodically - every 10s, which is quite aggressive.
GRPC server used by etcd implements a keep alive policy as a protection against the clients that ping too often. I believe it allows 2 pings in 2 hours by default.
The etcd's documentation states that this setting can be controlled via
--grpc-keepalive-min-time
configuration option, which is set to5s
by default:However, when my client sends pings every 10s, it receives exactly 3 pongs and then on 4th ping, the server responds with
too_many_pings
, which is exactly what would happen if the GRPC server used its own defaults, not the values provided by etcd.I'd appreciate any help getting it to work.
I tried setting
--grpc-keepalive-min-time
option from command line as well as adding it to config file, but it doesn't seem to have any effect, so I am either doing something wrong or I don't understand how this setting is supposed to work.Beta Was this translation helpful? Give feedback.
All reactions