Propagate readConcern::afterClusterTime from client to mongos to mongod

XMLWordPrintableJSON

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

      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 Stearn
            Reporter:
            Misha Tyulenev (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: