[SERVER-15028] prevent sync2.js from attempting an insert on a non-primary node Created: 25/Aug/14 Updated: 11/Jul/16 Resolved: 25/Aug/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | 2.7.5 |
| Fix Version/s: | 2.7.6 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Matt Dannenberg | Assignee: | Matt Dannenberg |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
This test starts with a replset of five nodes and then creates network partitions such that one node (node 4) is forced to sync through another (node 2, then after repartitioning a second time node 3). After each partition it ensures the write concern w:5 can be satisfied. The trouble is when all the nodes restart after enabling bridging (which allows for simulated network partitions), a node other than node 0 is briefly elected primary. This causes the write to node 0 to fail. I think adding an assert soon that waits for 0 to be primary again would fix this failure mode. |
| Comments |
| Comment by Githook User [ 25/Aug/14 ] |
|
Author: {u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}Message: |