Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-102677

Add finer granularity counters for why reopening a time-series bucket failed

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • Storage Execution 2025-03-31, Storage Execution 2025-04-14
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When we find an eligible time-series bucket on-disk to reopen for an insert, we perform some checks before bringing it back into memory in the bucket catalog here. At the moment, we increment a counter any time that one of these checks fail, but all of these different failures increment the same counter.

      It could be useful to additionally have some finer granularity counters around specific reasons that the checks failed (e.g. due to era mismatch, hash collision, or malformed bucket).

      This is a spin-off fromĀ SERVER-98672.

            Assignee:
            joseph.obaraye@mongodb.com Joseph Obaraye
            Reporter:
            damian.wasilewicz@mongodb.com Damian Wasilewicz
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:
              None
              None
              None
              None