[SERVER-53786] Test WriteConcernErrors are preserved with the mongos implementation of dropDatabases command Created: 14/Jan/21  Updated: 29/Oct/23  Resolved: 08/Feb/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.9.0

Type: Task Priority: Major - P3
Reporter: Samyukta Lanka Assignee: Shreyas Kalyan
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Security 2021-01-25, Security 2021-02-08, Security 2021-02-22
Participants:

 Description   

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.



 Comments   
Comment by Githook User [ 06/Feb/21 ]

Author:

{'name': 'Shreyas Kalyan', 'email': 'shreyas.kalyan@10gen.com', 'username': 'shreyaskalyan'}

Message: SERVER-53786 Test WriteConcernErrors are preserved with the mongos implementation of dropDatabases command
Branch: master
https://github.com/mongodb/mongo/commit/e55712f847134083ecd989e3f344ee3d87ec711c

Generated at Thu Feb 08 05:31:52 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.