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

Allow the router to send commitTransaction to all participants in parallel for single-write-shard transactions whose read-only participants have already made the reads durable

    XMLWordPrintableJSON

Details

    • Cluster Scalability
    • Fully Compatible

    Description

      If the router sees all the read-only shards have already committed their read Timestamp (by monitoring their last committed OpTimes through their ReplicaSetMonitors), the router could send commitTransaction to the read-only shards in parallel with sending commitTransaction to the write-shard, and only wait for the write-shard's response before returning the outcome to the client.

      Attachments

        Activity

          People

            backlog-server-cluster-scalability Backlog - Cluster Scalability
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated: