[SERVER-22806] CheckReplDBHash hook should fsync before doing await_repl Created: 23/Feb/16 Updated: 19/Nov/16 Resolved: 23/Feb/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | 3.3.2 |
| Fix Version/s: | 3.2.4, 3.3.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Robert Guo (Inactive) | Assignee: | Robert Guo (Inactive) |
| 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 | ||||
| Operating System: | ALL | ||||
| Backport Completed: | |||||
| Sprint: | TIG 11 (03/11/16) | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
CheckReplDBHash currently does does a w:<all_nodes> write to ensure all previous commands have replicated and that no commands are executed after running {{dbhash]}. But this does not guarantee that writes with w:0 close to the end of a test are treated correctly; they may still get inserted into the oplog after the CheckReplDBHash write. To fix this issue, it should be sufficient to do an fsync on the primary, given that the test fixture has exactly 2 nodes and no failover. |
| Comments |
| Comment by Githook User [ 24/Feb/16 ] |
|
Author: {u'username': u'guoyr', u'name': u'Robert Guo', u'email': u'robert.guo@10gen.com'}Message: (cherry picked from commit 3bf4d50da813dc877bba93a5356eb03430e828f6) |
| Comment by Githook User [ 23/Feb/16 ] |
|
Author: {u'username': u'guoyr', u'name': u'Robert Guo', u'email': u'robert.guo@10gen.com'}Message: |