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

Ensure mongos create command returns WriteConcern with higher precedence over NamespaceNotFound

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • CAR Team 2024-11-11, CAR Team 2024-11-25
    • 2

      Problem

      In the mongos create cmd code, we currently may return the createStatus error over any WriteConcern errors. This may lead to incompatibilities where we expect to retry on a WriteConcern error, but instead we fail due to the createStatus error being returned first.

      Solution & Acceptance Criteria

      We should prioritize sending any WriteConcern errors over other errors

      Impact

      This change leads to clearer and safer usage of the create command. It will also allow us to remove a workaround in mongosync where we manually handle NamespaceNotFound since it is send instead of a WriteConcern error

            Assignee:
            tommaso.tocci@mongodb.com Tommaso Tocci
            Reporter:
            xuerui.fa@mongodb.com Xuerui Fa
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated: