[SERVER-76872] MovePrimaryDonor Can Outlive MovePrimaryCoordinator Created: 05/May/23  Updated: 29/Oct/23  Resolved: 14/May/23

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 7.0.0-rc0, 7.1.0-rc0
Fix Version/s: 7.1.0-rc0, 7.0.0-rc1

Type: Bug Priority: Major - P3
Reporter: Brett Nawrocki Assignee: Brett Nawrocki
Resolution: Fixed Votes: 0
Labels: sharding-nyc-subteam1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
is related to SERVER-77115 Investigate Why move_primary_donor_cl... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v7.0
Sprint: Sharding NYC 2023-05-15
Participants:
Linked BF Score: 135

 Description   

The MovePrimaryCoordinator will attempt to find an existing MovePrimaryDonor after a step up. However, if the MovePrimaryCoordinator is already aborted while stepping up, _runImpl() is never called, instead proceeding immediately to _cleanupOnAbort(). In this case, the coordinator will never find the existing donor, and as a result never try to clean it up.



 Comments   
Comment by Githook User [ 15/May/23 ]

Author:

{'name': 'Brett Nawrocki', 'email': 'brett.nawrocki@mongodb.com', 'username': 'brettnawrocki'}

Message: SERVER-76872 Prevent donor from outliving MovePrimaryCoordinator

(cherry picked from commit 7ab0d365afc71fbd43b3583fae5424cfb8f7e1a8)
Branch: v7.0
https://github.com/mongodb/mongo/commit/5fe7a5f311547d773f9062b4d4f65725e49d853a

Comment by Githook User [ 13/May/23 ]

Author:

{'name': 'Brett Nawrocki', 'email': 'brett.nawrocki@mongodb.com', 'username': 'brettnawrocki'}

Message: SERVER-76872 Prevent donor from outliving MovePrimaryCoordinator
Branch: master
https://github.com/mongodb/mongo/commit/7ab0d365afc71fbd43b3583fae5424cfb8f7e1a8

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