[SERVER-42765] Specify priority/votes for rs members in read_pref_cmd.js to ensure stable primary/secondary Created: 12/Aug/19  Updated: 29/Oct/23  Resolved: 12/Sep/19

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.3.1

Type: Bug Priority: Major - P3
Reporter: Janna Golden Assignee: Janna Golden
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2019-09-23
Participants:
Linked BF Score: 8

 Description   

read_pref_cmd.js tests read preference and assumes that the same nodes will be primary/secondary throughout the entire test. If there is an unexpected stepdown, a different node could step up. We should ensure that the same node will always stepup by setting the priority and votes for each shard node in this test.



 Comments   
Comment by Githook User [ 12/Sep/19 ]

Author:

{'username': 'jannaerin', 'email': 'janna.golden@mongodb.com', 'name': 'Janna Golden'}

Message: SERVER-42765 Specify priority/votes for rs members in read_pref_cmd.js to ensure stable primary/secondary
Branch: master
https://github.com/mongodb/mongo/commit/0f44a7313df97e17665f6959164946d89c1f29b7

Generated at Thu Feb 08 05:01:22 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.