[
https://issues.apache.org/jira/browse/KUDU-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Wong updated KUDU-2929:
------------------------------
Fix Version/s: 1.12.0
Resolution: Fixed
Status: Resolved (was: In Review)
Fixed in
[bc4850f271236ef8722379ed1727568aff198fd9|https://github.com/apache/kudu/commit/bc4850f271236ef8722379ed1727568aff198fd9]
> Don't starve compactions under memory pressure
> ----------------------------------------------
>
> Key: KUDU-2929
> URL: https://issues.apache.org/jira/browse/KUDU-2929
> Project: Kudu
> Issue Type: Improvement
> Components: perf, tablet
> Reporter: Andrew Wong
> Assignee: Andrew Wong
> Priority: Major
> Fix For: 1.12.0
>
>
> When a server is under memory pressure, the maintenance manager exclusively
> will look for the maintenance op that frees up the most memory. Some
> operations, like compactions, do not register any amount of "anchored memory"
> and effectively don't qualify for consideration.
> This means that when a tablet server is under memory pressure, compactions
> will never be scheduled, even though compacting may actually end up reducing
> memory (e.g. combining many rowsets-worth of CFileReaders into a single
> rowset). While it makes sense to prefer flushes to compactions, it probably
> doesn't make sense to do nothing vs compact.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
