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

Loki Operator sets an invalid number of delete workers when using pico size

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • Logging 6.2.0
    • Logging 6.1.2, Logging 6.2.0
    • Log Storage
    • 2
    • False
    • None
    • False
    • NEW
    • VERIFIED
    • Before this update, an error in the Operator generating the Loki configuration caused the amount of delete workers to be zero, when using 1x.pico as LokiStack size. With this update, the number of delete workers is set to ten.
    • Bug Fix
    • Log Storage - Sprint 267

      Description of problem:

      The configuration generated by Loki Operator when using 1x.pico size sets retention_delete_worker_count to zero, causing Loki to not start any worker threads.

      This leads to the situation that Loki does not actually do any removal of data after the retention date anymore.

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

      6.1.2

      How to validate:

      Create a LokiStack using size: 1x.pico and check the generated ConfigMap for the retention_delete_worker_count item. It should be set to 10.

              rojacob@redhat.com Robert Jacob
              rojacob@redhat.com Robert Jacob
              Kabir Bharti Kabir Bharti
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: