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

    • Cluster Scalability
    • Fully Compatible
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              [DO NOT USE] Backlog - Cluster Scalability
              Reporter:
              Esha Maharishi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: