[SERVER-31954] Mark MMAPv1 storage engine as deprecated Created: 14/Nov/17 Updated: 30/Oct/23 Resolved: 07/Dec/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | MMAPv1 |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.1 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Alexander Gorrod | Assignee: | Neha Khatri |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Sprint: | Storage 2017-12-04, Storage 2017-12-18 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
The MMAPv1 storage engine is becoming increasingly outdated in terms of feature support, and the legacy code is becoming more expensive to maintain - we should deprecate MMAPv1, since WiredTiger is now the preferred storage engine. |
| Comments |
| Comment by Githook User [ 07/Dec/17 ] |
|
Author: {'name': 'nehakhatri5', 'email': 'neha.khatri@mongodb.com'}Message: |