[SERVER-40290] Race in last_vote.js Created: 22/Mar/19 Updated: 22/Mar/19 Resolved: 22/Mar/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | A. Jesse Jiryu Davis | Assignee: | A. Jesse Jiryu Davis |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 23 | ||||||||||||
| Description |
|
This test initiates a 2-node RS and restarts the secondary as standalone, then immediately stops the primary. Since the validate_collections_on_shutdown.js override is active, the test tries to validate all the collections on the primary before stopping it. If, during this validation, the primary notices that the secondary is no longer a member, then it steps down and collection validation fails with "InterruptedDueToStepDown". Pass skipValidation: true to ReplSetTest.stop() to avoid errors if the primary steps down before stopping.
|
| Comments |
| Comment by A. Jesse Jiryu Davis [ 22/Mar/19 ] |
|
Thanks Max! Yes, let's follow the path of |
| Comment by Max Hirschhorn [ 22/Mar/19 ] |
Skipping collection validation should always be an option of last resort because it may mean we fail to detect data inconsistencies. Does the work captured in |