[SERVER-55161] Tenant migration donor should always lock its mutex when setting its promises Created: 11/Mar/21  Updated: 29/Oct/23  Resolved: 16/Mar/21

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

Type: Bug Priority: Major - P3
Reporter: Jack Mulrow Assignee: Jack Mulrow
Resolution: Fixed Votes: 0
Labels: pm-1791_non-cloud-blocking, pm-1791_other_required
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2021-03-22
Participants:

 Description   

Tenant migration donor instances own several promises which can be set either by the instance's main run() chain or when interrupted on stepdown/shutdown. To avoid double setting a promise, wherever each promise is set, the donor should have locked its mutex.



 Comments   
Comment by Githook User [ 15/Mar/21 ]

Author:

{'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}

Message: SERVER-55161 Ensure tenant migration donor always locks mutex before setting its promises
Branch: master
https://github.com/mongodb/mongo/commit/4686af4495640257d02ddbb787ba3f2647b36255

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