Details
-
Task
-
Resolution: Works as Designed
-
Major - P3
-
None
-
None
-
None
-
None
Description
This is a follow up of https://jira.mongodb.org/browse/SERVER-36512 but this topic focuses on the issue happens after retriggering the issue of unlimited grows of lookaside table: WiredTigerLAS.wt.
Details see Issue of WiredTiger.wt grows unlimitedly is triggerable.pdf![]()
I want to ask:
1> Is it a bug that the WiredTigerLAS.wt cannot shrink to normal when the major data bearing member are available?
2> a question: If it is the designed behavior that the lookaside table: WiredTigerLAS.wt grows unlimitedly till it uses out all the diskspace if major data bearing members are not available.
If true, I would like to know if there is configuration option or something else to avoid WiredTigerLAS.wt stop halfway before it uses out all the disk space? As a user, I dislike this kind of behavior, I expect mongod can be smart enough to stop before the disk space used by WiredTigerLAS.wt reaching to a configured percent of disk space. Is this available or possible?
Thanks
Bruce