-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Minor Change
-
Sharding 2020-07-13, Sharding 2020-06-29, Sharding 2020-07-27, Sharding 2020-08-10, Sharding 2020-08-24, Sharding 2020-09-21
-
0
This task is to define appropriate vector clock timestamp classes for the objects stored in ShardRegistry and to implement it on top of ReadThroughCache in order to make it causally consistent.
- depends on
-
SERVER-46154 Make ReadThroughCache be driven by a vector clock
- Closed
-
SERVER-47406 Implement the persistence and tracking of a cluster `topologyTime`
- Closed
-
SERVER-48717 Implement the persist/recover functionalities of the VectorClock
- Closed
-
SERVER-49189 Make the ReadThroughCache lookup send the old entry state to the lookup function
- Closed
- is depended on by
-
SERVER-53533 Remove deprecated return value from ShardRegistry::reload
- Closed
- is related to
-
SERVER-50907 Shard objects should cache their own connection strings
- Closed
-
SERVER-50997 Make ShardRegistry::updateReplSetHosts() refresh synchronously
- Closed
-
SERVER-50908 Investigate if ShardNotFound special-case handling in migration recovery can be avoided
- Backlog
-
SERVER-50206 Remove "NoReload" ShardRegistry lookup functions
- Blocked
-
SERVER-50207 Investigate if ShardRegistry reads on configsvrs can always be majority
- Closed
-
SERVER-50906 Consider running shardRemovalHooks synchronously
- Closed
-
SERVER-50910 Make ShardRegistry::_getData() async
- Closed
- related to
-
SERVER-48201 ShardRegistry::reload() competes with updates to the ShardRegistry through the RSM
- Closed
-
SERVER-50209 ShardRegistry internal reload is not interruptible
- Closed
-
SERVER-52633 Remove unnecessary lookups during findShard operation in ShardRegistry
- Backlog
-
SERVER-52629 Apply lookup by ShardId first in non config shards
- Closed