You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
client-go sets minWatchTimeout to only 5min by default. Every watch will be terminated and reinitiated every 7.5min on average. This can translate to large WATCH QPS to API server on a large scale cluster with per node watch. For example, in a 10k cluster, it's constant 22 QPS even there is no event at all.
It's configurable through list options but I wonder is there downside to set it large?
The text was updated successfully, but these errors were encountered:
k8s-ci-robot
added
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
and removed
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
labels
Jul 28, 2024
client-go sets minWatchTimeout to only 5min by default. Every watch will be terminated and reinitiated every 7.5min on average. This can translate to large WATCH QPS to API server on a large scale cluster with per node watch. For example, in a 10k cluster, it's constant 22 QPS even there is no event at all.
It's configurable through list options but I wonder is there downside to set it large?
The text was updated successfully, but these errors were encountered: