[SERVER-67901] Stop gossiping lastCommittedOpTime in reply metadata Created: 08/Jul/22  Updated: 29/Oct/23  Resolved: 11/Jul/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Tommaso Tocci Assignee: Tommaso Tocci
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Gantt Dependency
has to be done before SERVER-67912 Reduce set of non-causally consistent... Closed
Related
is related to SERVER-33017 Add metadata hook to update lastCommi... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2022-07-11, Sharding EMEA 2022-07-25
Participants:

 Description   

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.



 Comments   
Comment by Githook User [ 09/Jul/22 ]

Author:

{'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}

Message: SERVER-67901 Stop gossiping lastCommittedOpTime in reply metadata
Branch: master
https://github.com/mongodb/mongo/commit/50debeeaead306533741f59336aa12cdef8052ac

Comment by Githook User [ 09/Jul/22 ]

Author:

{'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}

Message: SERVER-67901 Stop gossiping lastCommittedOpTime in reply metadata
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/14c37619ca231f886750dedd6a4ef93960f85ecf

Generated at Thu Feb 08 06:09:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.