[SERVER-24254] Wait for nodes to agree on primary in maxSyncSourceLagSecs.js and chaining_removal.js Created: 23/May/16 Updated: 18/Nov/16 Resolved: 24/May/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.10, 3.3.8 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Judah Schvimer |
| 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 | ||||
| Sprint: | Repl 15 (06/03/16) | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
Both of these tests can fail because they start trying to manipulate and assert each node's sync source before some nodes even know who the primary is. By waiting for the primary to be agreed upon, we avoid this race. |
| Comments |
| Comment by Githook User [ 06/Sep/16 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: (cherry picked from commit 60f64e0b438d268a07a517203990cb65a7ca5f60) |
| Comment by Githook User [ 24/May/16 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: |