-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
Sharding 2020-07-13, Sharding 2020-06-29, Sharding 2020-07-27, Sharding 2020-08-10
- Before deleting the MigrationCoordinatorDocument (here)
- Before writing the TransactionCoordinatorDocument (refer to SERVER-38918)
Upon some specific calls to ShardRegistry::reload(repurposed):
- depends on
-
SERVER-48717 Implement the persist/recover functionalities of the VectorClock
- Closed
-
SERVER-49400 Differenciate VectorClock persist behavior based on cluster role
- Closed
- is depended on by
-
SERVER-49193 Recover the VectorClock on shard primary step up
- Closed
- related to
-
SERVER-62243 Wait for vector clock document majority-commit without timeout
- Closed