Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-8579

Leader election lease acquisition always takes maximum time

XMLWordPrintable

    • Incidents & Support
    • False
    • Hide

      None

      Show
      None
    • False
    • Logging
    • NEW
    • NEW
    • Release Note Not Required
    • Logging - Sprint 283

      Description of problem: 

      The Loki Operator takes 2-3 minutes, which is the worst non-graceful lease acquisition time, to become operational after a pod restart due to leader election lease timeout. This affects operator availability during upgrades and redeployments.

      Version-Release number of selected component (if applicable): 

      How reproducible:

      Steps to Reproduce:

      1. Redeploy the loki operator with 
        make olm-undeply
        make olm-deploy
      1. Observe the Loki Operator pod logs

      Actual results:

      2-3 minutes of waiting time to acquire leader lease

      Expected results:

      It shouldn't always take the worst non-graceful timeout

      Additional info:

              Unassigned Unassigned
              btaani@redhat.com Bayan Taani
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: