XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • Thanos
    • Monitoring - Sprint 200, Monitoring - Sprint 201, Monitoring - Sprint 202

      Multi TSDB introduced the ability to run multiple TSDBs in one Thanos receive node allowing on disk multi-tenancy within the same process. During the migration we noticed an odd behavior, being a TSDB that was once started, will never be cleaned up if it's not actively ingesting samples. This is due to how compaction is triggered in TSDB, which only happens on `Commit` calls to the database.

      TSDBs whose data has been uploaded, and the WAL is empty, should be closed and not started on boot of the receive node.

            prekumar@redhat.com Prem Saraswat (Inactive)
            fbranczy@redhat.com Frederic Branczyk (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: