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

Mongos NoWritesPerformed errors MUST return original error

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Cluster Scalability
    • 0

      The existing behavior of mongos is to not propagate errors with the RetryableWriteError label, and instead retry internally. In this case, because the drivers cannot reliably maintain error handling logic for errors labeled with NoWritesPerfomed (that is drivers have no access to the original error), the internal behavior of mongos should be modified to meet the following condition:

      If a retry attempt fails with an error labeled NoWritesPerformed, mongos MUST return the original error.

            Assignee:
            backlog-server-cluster-scalability [DO NOT USE] Backlog - Cluster Scalability
            Reporter:
            preston.vasquez@mongodb.com Preston Vasquez
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: