-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
Sharding EMEA 2022-07-11, Sharding EMEA 2022-07-25
In SERVER-33017 we implemented a gossiping protocol to attach lastCommittedOpTime in every command reply. Additionally we were keeping track of the lastCommittedOpTime for each shard in their respective ShardRemote objects.
Both gossiping and tracking of this field is not necessary anymore and can be now removed.
Supposition: this field is not necessary anymore because the lastCommitedOpTime have been included in the hello command response.
- has to be done before
-
SERVER-67912 Reduce set of non-causally consistent API of the ShardRegistry
- Closed
- is related to
-
SERVER-33017 Add metadata hook to update lastCommittedOpTime on mongos
- Closed