[SERVER-30054] update tags.js to make nodes at indexes 3 and 4 unelectable Created: 07/Jul/17 Updated: 30/Oct/23 Resolved: 10/Jul/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.7, 3.5.10 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Benety Goh |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Backport Completed: | |||||||||
| Sprint: | Repl 2017-07-10 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
In tags.js, during some of the write concern tests, it is possible for the previously isolated node 4 to stand for election (see test case "partitions: [0-1-2] [1-4] [3-4]"), causing an unintended change in primary status. Setting the priority of one of the connected nodes to 4 will help to prevent an unexpected election from happening. |
| Comments |
| Comment by Githook User [ 12/Jul/17 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: (cherry picked from commit 19eee0ef7cbf41270f015c5206c823c3ac684725) |
| Comment by Githook User [ 10/Jul/17 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: |