Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-11759

Docs for SERVER-34779: Check the dbhash periodically in a new version of the replica_sets_jscore_passthrough.yml test suite

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0.0-rc1, 4.1.1
    • Component/s: None
    • Labels:
      None

      Description

      Description:

      The dbHash command now returns the names of any capped collections in a new "capped" field. The dbHash command also now returns the UUIDs associated with any collections in a new "uuids" field.

      Scope of changes:

      • 4.0
      • dbhash ref page
      • for now, won't reference in capped collections page since we tell people to use the isCapped() method to check if capped.

      Impact to other docs outside of this product:

      MVP:

      Resources:

      Engineering Ticket Description:

      We should create another version of jstests/libs/override_methods/run_check_repl_dbhash.js and possibly of ReplSetTest#checkReplicatedDataHashes() that doesn't require (1) flushing background indexes with collMod operations, (2) fsync+locking the primary, and (3) call ReplSetTest#awaitReplication(). A background thread inside of resmoke.py should then run the "dbhash" command periodically via the hook file and cause the test to be marked as a failure if a data inconsistency is detected.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              kay.kim Kay Kim (Inactive)
              Reporter:
              kay.kim Kay Kim (Inactive)
              Participants:
              Last commenter:
              Kay Kim Kay Kim (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                3 years, 31 weeks, 2 days ago
                Date of 1st Reply: