Uploaded image for project: 'OpenShift Top Level Product Strategy'
  1. OpenShift Top Level Product Strategy
  2. OCPPLAN-7577

minimize disruption from etcd leader elections

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • Product / Portfolio Work
    • False
    • False
    • Not Set
    • No
    • Not Set
    • Service Delivery
    • Not Set
    • Not Set
    • Undefined
    • OSD

      When etcd goes through a leader election by design all clients should fail fast and retry. The reason for this is during an election technically no leader exists so we can not server liniearized transaction. Instead of timing out fail fast and retry.

      Here is Clayton's take on the issue:

       https://docs.google.com/document/d/1FHH70woKNkrTw3fN7Ss7rNCkTX69WWSnArlrFN_ENGs/edit

              Unassigned Unassigned
              skolicha1@redhat.com Suresh Kolichala (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: