[SERVER-34778] Add support for specifying atClusterTime to the dbhash command Created: 01/May/18  Updated: 29/Oct/23  Resolved: 18/May/18

Status: Closed
Project: Core Server
Component/s: Storage, Testing Infrastructure
Affects Version/s: None
Fix Version/s: 4.0.0-rc0

Type: New Feature Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Max Hirschhorn
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-35017 Multi-document transactions do not re... Closed
is depended on by SERVER-34779 Check the dbhash periodically in a ne... Closed
Problem/Incident
causes SERVER-35253 `dbHash` can take locks in MODE_S whi... Closed
Related
related to SERVER-39169 Add testing-only support for doing sn... Closed
Backwards Compatibility: Fully Compatible
Sprint: TIG 2018-05-21, TIG 2018-06-04
Participants:
Linked BF Score: 0
Story Points: 3

 Description   

This makes it possible to detect transient data inconsistency failures (e.g. related to timestamping differences between the primary and secondary of a replica set) that have been resolved by the time we've finished waiting for all operations to have replicated. This requires changing the "dbhash" command to call getMinimumVisibleSnapshot(), etc. as AutoGetCollectionForRead does currently.



 Comments   
Comment by Githook User [ 18/May/18 ]

Author:

{'username': 'visemet', 'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com'}

Message: SERVER-34778 Add support for dbHash command inside multi-stmt txn.

The dbHash command is only allowed inside of a multi-statement
transaction when test commands are enabled.

Also introduces a WTPreserveSnapshotHistoryIndefinitely failpoint to
skip setting the oldest timestamp.
Branch: master
https://github.com/mongodb/mongo/commit/25b0e6f7d22de88faaa7e223195992e995acdff4

Generated at Thu Feb 08 04:37:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.