You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Tim Armstrong (Jira)" <ji...@apache.org> on 2020/10/09 00:07:00 UTC
[jira] [Updated] (IMPALA-662) Frontend runs out of memory when
generating many scan ranges
[ https://issues.apache.org/jira/browse/IMPALA-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Armstrong updated IMPALA-662:
---------------------------------
Labels: crash downgraded newbie ramp-up (was: crash downgraded ramp-up)
> Frontend runs out of memory when generating many scan ranges
> ------------------------------------------------------------
>
> Key: IMPALA-662
> URL: https://issues.apache.org/jira/browse/IMPALA-662
> Project: IMPALA
> Issue Type: Bug
> Components: Frontend
> Affects Versions: Impala 1.2
> Reporter: Skye Wanderman-Milne
> Priority: Major
> Labels: crash, downgraded, newbie, ramp-up
>
> When I set the scan range length to 2 bytes and queried a 200MB table, the frontend churned for several minutes (during which time I could not cancel the query) before the JVM ran out of memory and took down the impalad process. It would be nice if the frontend could somehow bail in this situation, or at least be cancellable. This is an extreme case and I'm not sure at what point the FE falls over, but this could theoretically be an issue with a sane scan range length and many files (or just a huge amount of data).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org