Description of problem:
While working on the readiness probes we have discovered that the single member health check always allocates a new client. Since this is an expensive operation, we can make use of the pooled client (that already has a connection open) and change the endpoints for a brief period of time to the single member we want to check. This should reduce CEO's and etcd CPU consumption.
Version-Release number of selected component (if applicable):
any supported version
How reproducible:
always, but technical detail
Steps to Reproduce:
na
Actual results:
CEO creates a new etcd client when it is checking a single member health
Expected results:
CEO should use the existing pooled client to check for single member health
Additional info:
- blocks
-
OCPBUGS-38574 [4.17] use pooled client for etcd single member health checks
- Closed
- is cloned by
-
OCPBUGS-38574 [4.17] use pooled client for etcd single member health checks
- Closed
- links to
-
RHEA-2024:6122 OpenShift Container Platform 4.18.z bug fix update
(1 links to)