[DOCS-10541] Docs for SERVER-29277: Two Phase Drops: implement dropDatabase changes to support 2-phase drops Created: 18/Jul/17  Updated: 29/Oct/23  Resolved: 17/Oct/17

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: 3.5.10

Type: Task Priority: Major - P3
Reporter: Emily Hall Assignee: Pavithra Vetriselvan
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-29277 Two Phase Drops: implement dropDataba... Closed
Related
related to DOCS-11488 Document that dropDatabase in 3.6 now... Closed
Participants:
Days since reply: 6 years, 18 weeks ago
Epic Link: DOCS: 3.6 Server

 Description   

Documentation Request Summary:

No documentation summary in engineering ticket

Engineering Ticket Description:

Collection drops are deferred until commit point advances to or past optime of drop operation. For database drops, we wait until all the collection drops are committed. While we are waiting for the collection drops to be committed, any writes to the database will be rejected. While the collection drop oplog entries are written to the oplog before they enter the drop-pending state, the dropDatabase oplog entry is only written to the oplog when all the collection drops are committed.



 Comments   
Comment by Githook User [ 12/Oct/17 ]

Author:

{'email': 'pavi@MacBook-Pro-77.local', 'name': 'Pavithra Vetriselvan'}

Message: DOCS-10541 added two phase drop to dropDatabase command docs
Branch: master
https://github.com/mongodb/docs/commit/6637fa8574f192cb4c3880473d63b075f12adc03

Generated at Thu Feb 08 08:00:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.