-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
ALL
-
Sharding 2021-04-05
-
155
-
1
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.
- is caused by
-
SERVER-55289 Move RecipientStateMachine methods accessing resharding data replication components behind an interface
- Closed
- related to
-
SERVER-55813 ReshardingDataReplication may still emplace _consistentButStale more than once
- Closed