Note: this ticket was reverted for 8.1 and 8.0.6 due to SERVER-101739
Currently, the Time definition of the ShardRegistry has some flaws:
- no total order: potential causal consistency breakage (timeInStore overwriting a newer topologyTime).
- Null topologyTime cause the topologyTime component to be ignored. In the absence of forceReloads or rsmIncrements, the topologyTime in VectorClock never advances timeInStore.
The Time definition should be reworked to address these issues.
- is depended on by
-
SERVER-91121 Do not force a Shard Registry lookup if topology time doesn't change
-
- Closed
-
- is related to
-
-
- Closed
-
- related to
-
SERVER-96756 Check the behavior of the ShardRegistry with the new time definition in a scenario without topology times
-
- Closed
-
-
-
- Closed
-