[ https://issues.apache.org/jira/browse/IMPALA-7096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on IMPALA-7096 started by Tim Armstrong. --------------------------------------------- > Ensure no memory limit exceeded regressions from IMPALA-4835 because of > non-reserved memory > ------------------------------------------------------------------------------------------- > > Key: IMPALA-7096 > URL: https://issues.apache.org/jira/browse/IMPALA-7096 > Project: IMPALA > Issue Type: Bug > Components: Backend > Affects Versions: Impala 2.13.0, Impala 3.1.0 > Reporter: Tim Armstrong > Assignee: Tim Armstrong > Priority: Blocker > Labels: resource-management > Attachments: ScanConsumingMostMemory.txt > > > IMPALA-7078 showed some cases where non-buffer memory could accumulate in the > row batch queue and cause memory consumption problems. > The decision for whether to spin up a scanner thread in IMPALA-4835 > implicitly assumes that buffer memory is the bulk of memory consumed by a > scan, but there may be cases where that is not true and the previous > heuristic would be more conservative about starting a scanner thread. > We should investigate this further and figure out how to avoid it if there's > an issue. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org