ExportXMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      dbcheck_logs_minkey_maxkey.js writes to the secondary in standalone mode to introduce corruption, then asserts dbCheck's health log catches it with the expected minKey/maxKey entries. It was exempted from rid-enabled collections via overrideRecordIdsReplicatedFalse as the expedient fix for SERVER-118527. This ticket was the "decide and fix properly" follow-up.

      Change

      Delete the failpoint. Under the groupId design the exemption is no longer needed:

      • dbCheck is rid-agnostic by design, so health log batch entries (minKey/maxKey) are unaffected by rids.
      • The standalone write that introduces the corruption now also clears the secondary's groupId via C4 (SERVER-138309), which is the correct semantics for a node written outside replication. The test already sets TestData.skipCheckDBHashes, so the resulting out-of-group state does not trip fixture hash checks.

      This resolves the original refactor question in the "make it compatible" direction: no rrid-specific handling is required because dbCheck never sees rids.

      Acceptance criteria

      • The test passes with the failpoint removed, in default and all-feature-flags variants.
      • The corruption it introduces is still caught with the same minKey/maxKey health log entries.

            Assignee:
            Unassigned
            Reporter:
            Yuhong Zhang
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: