[SERVER-25273] Concurrency suite dbHash check should call checkDBHashesFsyncLocked Created: 25/Jul/16  Updated: 21/Nov/16  Resolved: 26/Jul/16

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 3.2.9, 3.3.11

Type: Task Priority: Major - P3
Reporter: Jonathan Abrahams Assignee: Jonathan Abrahams
Resolution: Done Votes: 0
Labels: test-only
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-25274 Make checkDBHashesFsyncLocked from js... Closed
Backwards Compatibility: Fully Compatible
Backport Completed:
Sprint: TIG 18 (08/05/16)
Participants:
Linked BF Score: 0

 Description   

The concurrency suite should invoke checkDBHashesFsyncLocked from the jstests/hooks/check_repl_dbhash.js instead of checkDBHashes. The additional logic in the concurrency suite to prevent the TTL monitor from deleting expired documents in the background can be removed, as it is now handled in the hook.



 Comments   
Comment by Githook User [ 26/Jul/16 ]

Author:

{u'username': u'hptabster', u'name': u'Jonathan Abrahams', u'email': u'jonathan@mongodb.com'}

Message: SERVER-25273 Concurrency suite dbHash check should call checkDBHashesFsyncLocked
Branch: v3.2
https://github.com/mongodb/mongo/commit/ac162ebc53af7296f7837b2f57fc0cf92c001393

Comment by Githook User [ 26/Jul/16 ]

Author:

{u'username': u'hptabster', u'name': u'Jonathan Abrahams', u'email': u'jonathan@mongodb.com'}

Message: SERVER-25273 Concurrency suite dbHash check should call checkDBHashesFsyncLocked
Branch: master
https://github.com/mongodb/mongo/commit/388143b96f3eae05f07596c3f5e428e3d3e01175

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