[SERVER-37213] small cache size causes hangs in rollback_wt_cache_full.js in 3.6 Created: 19/Sep/18 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 3.6.8 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Backlog - Storage Engines Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | storage-engines | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Engines
|
||||||||
| Participants: | |||||||||
| Description |
|
The cache size in rollback_wt_cache_full.js is currently set to 1 GB. We should look into lowering this cache size, at least on the 3.6 branch, to a setting that is closer to the built-in rollback refetch limit of 300 MB. |
| Comments |
| Comment by Sara Williamson [ 15/Nov/18 ] |
|
We don't need to take any action right now – this can be deprioritized. We'll revisit after the other replication cache issues have been addressed. |
| Comment by Alexander Gorrod [ 06/Nov/18 ] |
|
Setting a cache size smaller than 1GB is certainly reasonable. There is an upper limit of 20% of cache used for dirty content - which this test is configuring. That translates to 200MB with 1GB. The test is using 10MB documents - so it'll be necessary to keep the cache size large enough to hold a reasonable number of those very large docs. I wouldn't use a cache size of less than 300MB (60MB dirty) for the test as it was committed. |
| Comment by Benety Goh [ 05/Nov/18 ] |
|
alexander.gorrod, the issue isn't with figuring how to set a smaller cache size. We were wondering if it makes sense to run this test with a 0.5GB cache size to match some customers' deployments and determine if this test will still run well. |
| Comment by Alexander Gorrod [ 05/Nov/18 ] |
|
benety.goh is the question here about how to set a cache size smaller than 1GB? If so - the cache size configuration option is a float to allow setting smaller cache sizes. If not could you please clarify the intent of this ticket? |