[SERVER-55723] ReshardingDataReplication may emplace _consistentButStale more than once Created: 01/Apr/21  Updated: 29/Oct/23  Resolved: 02/Apr/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 5.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Max Hirschhorn
Resolution: Fixed Votes: 0
Labels: PM-234-M2.5
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Problem/Incident
is caused by SERVER-55289 Move RecipientStateMachine methods ac... Closed
Related
related to SERVER-55813 ReshardingDataReplication may still e... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2021-04-05
Participants:
Linked BF Score: 155
Story Points: 1

 Description   

It is possible for _consistentButStale.emplaceValue() to be called after ensureFulfilledPromise(_consistentButStale, originalError) has already been called. This is due to whenAllSucceed() returning a future ready with an error status if one of the data replication components has errored. ReshardingDataReplication should instead call ensureFulfilledPromise(_consistentButStale, originalError) after waiting for the future return by whenAll() to become ready.



 Comments   
Comment by Githook User [ 01/Apr/21 ]

Author:

{'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com', 'username': 'visemet'}

Message: SERVER-55723 Quiesce before fulfilling in ReshardingDataReplication.
Branch: master
https://github.com/mongodb/mongo/commit/c8e74f9e82a9aab3f549ff77aa539fa6b3ab6b45

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