[SERVER-34024] Disable WiredTiger cursor cache by default. Created: 21/Mar/18 Updated: 07/Dec/23 Resolved: 22/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.4, 3.7.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Alexander Gorrod | Assignee: | Alexander Gorrod |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Backport Requested: |
v3.6
|
||||||||||||
| Sprint: | Storage Non-NYC 2018-03-26 | ||||||||||||
| Participants: | |||||||||||||
| Case: | (copied to CRM) | ||||||||||||
| Description |
|
WIredTiger recently added a new feature to cache WT_CURSOR handles. The option enables caching by default, but MongoDB doesn't need a WiredTiger cursor cache, since it implements one of it's own. We should disable the WiredTiger cursor cache via a configuration option in MongoDB. |
| Comments |
| Comment by Githook User [ 22/Mar/18 ] |
|
Author: {'email': 'alexander.gorrod@mongodb.com', 'name': 'Alex Gorrod', 'username': 'agorrod'}Message: We are still using the MongoDB caching, so no need to double up. |
| Comment by Githook User [ 22/Mar/18 ] |
|
Author: {'email': 'alexander.gorrod@mongodb.com', 'name': 'Alex Gorrod', 'username': 'agorrod'}Message: We are still using the MongoDB caching, so no need to double up. |