Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-38574

[4.17] use pooled client for etcd single member health checks

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Undefined Undefined
    • None
    • 4.14, 4.15, 4.16, 4.17, 4.18
    • Etcd
    • None
    • False
    • Hide

      None

      Show
      None
    • N/A
    • Release Note Not Required
    • Done

      This is a clone of issue OCPBUGS-38573. The following is the description of the original issue:
      —
      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:

              dwest@redhat.com Dean West
              openshift-crt-jira-prow OpenShift Prow Bot
              Ge Liu Ge Liu
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: