mongos does not return WriteConcernError in renameCollection

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • ALL
    • Hide
      • 3-node ReplSetTest vs 3-node shard:
      • Stop one secondary replica to force timeout
      • Run renameCollection with writeConcern ` {w:3, wtimeout: 1000}

        `

      Show
      3-node ReplSetTest vs 3-node shard: Stop one secondary replica to force timeout Run renameCollection with writeConcern ` {w:3, wtimeout: 1000} `
    • CAR Team 2024-12-09
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Using the pattern in tests jstests/replsets/noop_writes_wait_for_write_concern.js and jstests/sharding/mongos_noop_writes_wait_for_write_concern.js, we can see that renameCollection does return a WriteConcernError in the replset but mongos does not return WriteConcernError.

            Assignee:
            Pierlauro Sciarelli
            Reporter:
            Israel Hsu (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: