Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-64344

Do not use atClusterTime when refreshing routing table on config server

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 6.0.0-rc0
    • None
    • None
    • None
    • Fully Compatible
    • Sharding EMEA 2022-03-21

    Description

      Currently on each collection refresh performed by a node of the CSRS we perform an aggregation with a snapshotReadConcern with an atClusterTime equal to the last locally applied optime. This means that every time we perform a collection refresh we will need to wait for the latest applied op time to be majority committed before we can take the snapshot.

      Instead we could simply use a snapshotReadConcern without specifying any cluster time so that we will read from the latest committed snapshot.

      Attachments

        Activity

          People

            tommaso.tocci@mongodb.com Tommaso Tocci
            tommaso.tocci@mongodb.com Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: