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

Set number of minimum available pods dynamically based on replication factor

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Normal Normal
    • Logging 6.4.0
    • Logging 6.2.0, Logging 6.3.0, Logging 5.8.z, Logging 5.9.z, Logging 6.0.z, Logging 6.1.z
    • Log Storage
    • None
    • Product / Portfolio Work
    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • NEW
    • NEW
    • If Release Note Needed, Set a Value
    • Logging - Sprint 278

      Currently the "minimum available pods" for each Deployment / StatefulSet created by the Loki Operator is a static value determined by the selected LokiStack size. For most Deployments / StatefulSets only a single instance needs to be kept alive to theoretically achieve high-availability.

      The ingester behaves differently though and needs a certain minimum number of available instances based on the selected replication factor.

      Currently a valid configuration is achieved by setting a default value for the minimum availability based on the selected size and its default replication factor. This works as long as the replication factor is not changed from that default.

      The goal of this story is to implement the minimum availability as a dynamic value based on the selected replication factor instead and get rid of the default value set based on size.

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

                Created:
                Updated: