[SERVER-55813] ReshardingDataReplication may still emplace _consistentButStale more than once Created: 06/Apr/21  Updated: 29/Oct/23  Resolved: 08/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
Related
related to SERVER-67466 Internal transactions API may be memo... Closed
is related to SERVER-55723 ReshardingDataReplication may emplace... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2021-04-19
Participants:
Linked BF Score: 155
Story Points: 1

 Description   

The changes from c8e74f9 as part of SERVER-55723 were insufficient. An issue remains that this part of the future chain isn't being joined by the whenAll() / whenAllSettledOn() which comes later in the future chain. It is also possibe for chainCtx->oplogApplierConsistentButStaleFutures and chainCtx->oplogApplierStrictlyConsistentFutures to be reassigned while the whenAllSettledOn() are attempting to wait on them (read: data race).



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

Author:

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

Message: SERVER-55813 Fix quiescing future chain in ReshardingDataReplication.
Branch: master
https://github.com/mongodb/mongo/commit/518af1a5c2189882acaf1f41726aeaf3fd0c1f76

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