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

Test WriteConcernErrors are preserved with the mongos implementation of drop command

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.9.0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Fully Compatible
    • Security 2021-01-25, Security 2021-02-08

      We can use a failpoint on mongod to return a write concern error and see how mongos handles the error. See jstests/sharding/transactions_error_labels.js for an example.

      If it does not preserve WriteConcernErrors, we should convert the command to inherit from BasicCommandWithRequestParser instead. See the implementation for commitTransaction as an example.

            Assignee:
            shreyas.kalyan@mongodb.com Shreyas Kalyan
            Reporter:
            samy.lanka@mongodb.com Samyukta Lanka
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: