Details
-
Task
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
None
-
None
-
None
Description
Description:
Updated the shell drop() helper (https://docs.mongodb.com/manual/reference/method/db.collection.drop/) to take parameters like write concern, e.g.,
testDB.testColl.drop({writeConcern: {w: "majority"}});
Previously the shell helper rejected any parameters. Committed to v4.0 and v4.1
Scope of changes:
- drop command
- drop helper
- release notes
- in addition, txn and txn-production-considerations – if run immediately before txn start (in lock section)
Impact to other docs outside of this product:
none
MVP:
Resources:
Engineering Ticket Description:
collation.js, misc_validation.js, do_txn_basic.js (per BF-9138) all need to be fixed to wait for both phases of two-phase drop to finish before starting transaction ops. Per SERVER-34372 and SERVER-33244, using majority write concern in an op will wait for the second phase of drop to finish before beginning the command, so that transaction ops don't run into lock conflict that cause the op (and entire transaction) to abort. Majority write concern should be added to the drop cmds.
Attachments
Issue Links
- documents
-
SERVER-34991 JS tests doing transaction operations must use majority writeConcern for drops
-
- Closed
-
- is related to
-
DOCS-11505 Document Transactions
-
- Closed
-
- related to
-
DOCS-11585 Mongos uses majority writeconcern for all metadata operations
-
- Closed
-