[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:
Related
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: SERVER-22152 wait for high priority node to become primary at beginning of test

(cherry picked from commit 23323e6f1a9074ade844fe364feb121d7b4d8a32)
Branch: v3.2
https://github.com/mongodb/mongo/commit/d04d195125a020c2eb75a884daa1cb190db08fb7

Comment by Githook User [ 13/Jan/16 ]

Author:

{u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}

Message: SERVER-22152 wait for high priority node to become primary at beginning of test
Branch: master
https://github.com/mongodb/mongo/commit/23323e6f1a9074ade844fe364feb121d7b4d8a32

Generated at Thu Feb 08 03:59:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.