[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: |
|
||||||||
| 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: |
| Comment by Githook User [ 26/Jul/16 ] |
|
Author: {u'username': u'hptabster', u'name': u'Jonathan Abrahams', u'email': u'jonathan@mongodb.com'}Message: |