Add logging to provide visibility into double-registering drop-pending idents in the storage engine's reaper

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • Storage Execution 2026-05-11
    • 200
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      BF-42904 was raised due to an invariant in `addDropPendingIdent()` expecting that the ident is not already being tracked as drop-pending.  This only occured once in jsfuzztests on the index-build abort path on the constraint-violations ident. Since it hasn't been able to be reproduced, we need to add some additional logging to `addDropPendingIdent()` concerning "internal-constraintViolations-"so that the next time this happens we will capture more information.

            Assignee:
            Binh Vo
            Reporter:
            Binh Vo
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: