[SERVER-46627] Secondaries with 'newlyAdded' field should be effectively 'priority:0' Created: 04/Mar/20  Updated: 29/Oct/23  Resolved: 26/Mar/20

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.7.0

Type: Task Priority: Major - P3
Reporter: Judah Schvimer Assignee: Xuerui Fa
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Repl 2020-03-23, Repl 2020-04-06
Participants:

 Description   

Right after leaving initial sync, nodes will be secondaries and have a 'newlyAdded' field. These nodes should be unelectable.

'newlyAdded' nodes should also always be treated as 'priority:0' for calculating priority rank.



 Comments   
Comment by Githook User [ 26/Mar/20 ]

Author:

{'email': 'xuerui.fa@mongodb.com', 'name': 'Xuerui Fa', 'username': 'XueruiFa'}

Message: SERVER-46627: Ensure secondaries with 'newlyAdded' field have priority: 0
Branch: master
https://github.com/mongodb/mongo/commit/12e5e201689e082f1b3a43f14bc2adccf4f75875

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