local.replset.minvalid writes are untimestamped but may fail if encountering a timestamped entry in the ident beforehand

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: 7.0.0, 8.0.0
    • Component/s: None
    • Catalog and Routing
    • Fully Compatible
    • v8.2, v8.0, v7.0
    • CAR Team 2025-08-04, CAR Team 2025-08-18
    • 0
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In the course of SERVER-104334 we discovered that the writes being done to the local.replset.minvalid collection are untimestamped but do not indicate so to the RecoveryUnit.

      Today this isn't an issue if there are no timestamped entries in the collection since WT will not complain about it. However, if a server undergoes rapid succession of server upgrades it may encounter such a case and lead to the node crashing at startup.

              Assignee:
              Jordi Olivares Provencio
              Reporter:
              Jordi Olivares Provencio
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: