[SERVER-42524] Remove the "touch" command Created: 31/Jul/19 Updated: 29/Oct/23 Resolved: 25/Sep/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Haley Connelly |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Minor Change | ||||||||||||
| Sprint: | Execution Team 2019-09-23, Execution Team 2019-10-07 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
The "touch" command is supposed to pull all data into cache. Only MMAP supported "touch". See docs. The "inMemory" and "ephemeralForTest" storage engines do support the command, but they just return "OK" as a no-op. All other storage engines, including WiredTiger, return an error, so there's no need to deprecate the command first. The functionality of "touch" can be implemented by "warming up" the cache with collection and index scans. |
| Comments |
| Comment by Githook User [ 25/Sep/19 ] |
|
Author: {'name': 'Haley Connelly', 'username': 'haleyConnelly', 'email': 'haley.connelly@10gen.com'}Message: |