[SERVER-29280] Two Phase Drops: all drop-pending collections must be dropped immediately upon downgrade to 3.4 Created: 18/May/17  Updated: 10/Jul/17  Resolved: 12/Jun/17

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

Type: Task Priority: Major - P3
Reporter: Benety Goh Assignee: Judah Schvimer
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-29274 Two Phase Drops: rename collection to... Closed
Duplicate
duplicates SERVER-29569 Store the featureCompatibilityVersion... Closed
Related
related to SERVER-30082 Two Phase Drops: remove all drop-pend... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2017-06-19
Participants:

 Description   

This new two-phase-drop behavior will be enabled by setFeatureCompatibilityVersion, since it will work in concert with new rollback behavior that is in kind enabled by that command. Upon downgrading to 3.4 feature mode, the code can immediately drop all drop-pending collections. Subsequent downgrades to 3.4 mongod binaries should have no further effects.



 Comments   
Comment by Judah Schvimer [ 12/Jun/17 ]

The w:majority write on featureCompatibilityVersion downgrade should be sufficient to make sure all of the drop-pending collections are dropped. SERVER-29569 is required to make this process not racy though.

Generated at Thu Feb 08 04:20:23 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.