Every time a shard is added or removed, we create a new topologyTime (let's call it T0 time) that is inserted in config.shards. Afterwards, when this operation is locally committed (let's say that at Tcommit time), we store the value of T0 time in a in-memory data structure. Finally, when the majority commit point is advanced to a TmajorityPoint time greater or equal than T0 time, we tick the configTime and advance the vector clock topologyTime to the T0 time.
The problem of this approach is that we are advancing the topologyTime of the vector clock when TmajorityPoint >= T0, but this doesn't guarantee that the time associated to the oplog entry (i.e. Tcommit) was majority committed. Thus, we might end up gossiping a new topologyTime but when we a shard goes to the config server expecting to find an entry in config.shards with a topologyTime of T0, it might happen that it doesn't find it.
Note that the topologyTime is a time but it doesn't provide any guarantee about what you will find in config.shards. It could be seen just as a counter that it is ticked every time we perform an add/remove shard operation.
- is depended on by
-
SERVER-64408 VectorClock's topology time may be wrongly advanced in case of rollback
-
- Closed
-
- is related to
-
-
- Closed
-
-
-
- Closed
-
- related to
-
SERVER-89272 Investigate why the config.shards insert on initial sync node in config shard doesn't have commit timestamp
-
- Blocked
-
-
SERVER-64627 Need general method to handle in-memory state after initial sync
-
- Closed
-