[SERVER-22152] priority_takeover_two_nodes_equal_priority.js fails if default priority node gets elected at beginning of test Created: 12/Jan/16 Updated: 25/Jan/17 Resolved: 13/Jan/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.3, 3.3.1 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Benety Goh | Assignee: | Benety Goh |
| 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: | |||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
Test case description expects 3 electable nodes - 2 with priority 3 and 1 with default priority. It's possible that the default priority node gets elected as primary at the beginning of the test. The test should wait for one of the higher priority nodes to take over as primary before proceeding. |
| Comments |
| Comment by Githook User [ 29/Jan/16 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: (cherry picked from commit 23323e6f1a9074ade844fe364feb121d7b4d8a32) |
| Comment by Githook User [ 13/Jan/16 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: |