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

Propagate readConcern::afterClusterTime from client to mongos to mongod

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: Needs Triage
    • Component/s: Sharding
    • Labels:
      None
    • Fully Compatible

      Currently readConcern is carried by the ServerSelectionMetadata and as it gets rebuilt it may lose afterClusterTime argument that will affect causalConsistency.
      The fix need to ensure that the afterClusterTime provided by the client gets propagated all the way to mongod.

            Assignee:
            mathias@mongodb.com Mathias Stearn
            Reporter:
            misha.tyulenev@mongodb.com Misha Tyulenev
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: