[SERVER-54748] Does not change priority of one of the node in MongoDB replica set. Created: 24/Feb/21  Updated: 24/Feb/21  Resolved: 24/Feb/21

Status: Closed
Project: Core Server
Component/s: Admin, Replication
Affects Version/s: 3.4.2
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Nagesh Dnyandeo Kamble Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

Hi Team,

In our existing MongoDB Replica cluster , we have a 3-node replica set that was running with a configuration of priority 0.5 - 0.5 - 1.

We tried to change priority for two nodes from 0.5 to 1 to make it equivalent for all three node as "1" using rs.conf() and rs.reconfig().

But we get success in changing only one node priority from 0.5 to 1.

Even though configuration and re-configuration command successfully executed. Why not one node priority changed in configuartion.

It's showing only 0.5 and cluster priority becomes 0.5-1-1. 

 

Again next thing we come to notice that, one of the node which was primary in running change its priority from 1 to 2. 

We look log it's showing "Scheduling priority takeover at -----" during that time.

And finally, cluster priority becomes "2-1-0.5"  which is not our desired required output.

Kindly help us to understand the issue and why it happened.

 

 



 Comments   
Comment by Dmitry Agranat [ 24/Feb/21 ]

Hi n.kamble@pokermagnet.com,

MongoDB 3.4 reached end of life in January of 2020. As for general questions about how priorities work in MongoDB, we'd like to encourage you to start by asking our community for help by posting on the MongoDB Developer Community Forums.

Regards,
Dima

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