[SERVER-31666] catchup_takeover_one_high_priority should use initiateWithAnyNodeAsPrimary Created: 20/Oct/17  Updated: 30/Oct/23  Resolved: 17/Feb/18

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.6.4, 3.7.3

Type: Improvement Priority: Major - P3
Reporter: Matthew Russotto Assignee: Vesselina Ratcheva (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.6
Sprint: Repl 2018-02-26
Participants:
Linked BF Score: 0

 Description   

It's inherently racy to use initiate() with a high priority node other than node 0.



 Comments   
Comment by Githook User [ 27/Mar/18 ]

Author:

{'email': 'vesselina.ratcheva@10gen.com', 'name': 'Vesselina Ratcheva', 'username': 'vessy-mongodb'}

Message: SERVER-31666 use initiateWithAnyNodeAsPrimary in catchup_takeover_one_high_priority.js

(cherry picked from commit fea4cfc5719897a82b2e1dd7b68f94fb3990228f)
Branch: v3.6
https://github.com/mongodb/mongo/commit/9f24380380b579815ec15fd8b761b1df63e8ad98

Comment by Githook User [ 17/Feb/18 ]

Author:

{'email': 'vesselina.ratcheva@10gen.com', 'name': 'Vesselina Ratcheva', 'username': 'vessy-mongodb'}

Message: SERVER-31666 use initiateWithAnyNodeAsPrimary in catchup_takeover_one_high_priority.js
Branch: master
https://github.com/mongodb/mongo/commit/fea4cfc5719897a82b2e1dd7b68f94fb3990228f

Comment by Spencer Brody (Inactive) [ 14/Feb/18 ]

vesselina.ratcheva, can you take a crack at this on Friday?

Generated at Thu Feb 08 04:27:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.