TTLMonitor does unnecessary work on secondaries

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • Execution Team 2024-11-11, Execution Team 2024-11-25, Execution Team 2024-12-09
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The TTLMonitor has reports metrics for each ttl passess and subpasses. However, the TTLMonitor utilizes replicated deletes, and should only be run when the node is primary.

      However, the TTLMonitor checks late on whether it is primary. At that point, scope guards will auto-increment 'passess' and 'subpassess'.

      This is misleading from an observability perspective - the TTLMonitor appears to be running on secondaries, but doesn't perform any real work.

            Assignee:
            Binh Vo
            Reporter:
            Haley Connelly
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: