You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #6363 we are fixing versionMap to clear on refresh not flush, but even once we fix that, if the user sets a big refresh (or turns it off), and big xlog flush triggers, then the versionMap can grow unbounded. I think we should trigger refresh once versionMap is too large?
The text was updated successfully, but these errors were encountered:
If the user sets a high refresh interval, the versionMap can use
unbounded RAM. I fixed LiveVersionMap to track its RAM used, and
trigger refresh if it's > 25% of IW's RAM buffer. (We could add
another setting for this but we have so many settings already?).
I also fixed deletes to prune every index.gc_deletes/4 msec, and I
only save a delete tombstone if index.gc_deletes > 0.
I think we could expose the RAM used by versionMap somewhere
(Marvel? _cat?), but we can do that separately ... I put a TODO.
Closeselastic#6378
clintongormley
changed the title
If versionMap is too large we should trigger refresh
Indexing: If versionMap is too large we should trigger refresh
Jul 16, 2014
In #6363 we are fixing versionMap to clear on refresh not flush, but even once we fix that, if the user sets a big refresh (or turns it off), and big xlog flush triggers, then the versionMap can grow unbounded. I think we should trigger refresh once versionMap is too large?
The text was updated successfully, but these errors were encountered: