Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Minor - P4
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: WT2.6.0
-
Labels:None
Description
We have never tested what it means to configure LSM and cache_resident at the same time.
Configuring both is likely to stop the process of moving the in-memory chunks to disk - limiting the number of chunks to how much fits into cache.
That may be expected behavior - if so we should consider documenting and close this issue.
Activity
The change to implement this is in code review here:
https://github.com/wiredtiger/wiredtiger/pull/1937
Author:
{u'username': u'agorrod', u'name': u'Alex Gorrod', u'email': u'alexg@wiredtiger.com'}Message: Disallow the cache_resident flag on LSM trees.
Refs WT-1905
Branch: develop
https://github.com/wiredtiger/wiredtiger/commit/3cfca1a09f6f5879f007d51071e4c1feb5d454b9
Enforced that cache_resident isn't set on LSM trees, and updated documentation.
I think we should disallow cache_resident on LSM trees – I talked this over with Keith Bostic late last week. It doesn't make much sense, since LSM is all about managing data that is too large for cache with sequential I/O.