drop/dropDatabase: Mongos WriteConcernError Behavior Differs from Mongod

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • ALL
    • CAR Team 2024-12-09
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The changes for SERVER-78311 introduces mongos_noop_writes_wait_for_write_concern.js, a variant of noop_writes_wait_for_write_concern.js that goes through mongos. SERVER-78311 addresses inconsistencies that caused the update/insert commands to fail, but there are still a number of commands whose tests cases are disabled due to differing behavior.

      This ticket is specifically to investigate/address drop <collection> and dropDatabase commands.

            Assignee:
            Pierlauro Sciarelli
            Reporter:
            Adi Zaimi
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: