[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: |
|
||||||||||||||||||||||||
| 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. |