Stop gossiping lastCommittedOpTime in reply metadata

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Sharding EMEA 2022-07-11, Sharding EMEA 2022-07-25
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              Tommaso Tocci
              Reporter:
              Tommaso Tocci
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: