[
https://issues.apache.org/jira/browse/IMPALA-6597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong resolved IMPALA-6597.
-----------------------------------
Resolution: Duplicate
> Inert into partitioned runs out of memory
> -----------------------------------------
>
> Key: IMPALA-6597
> URL: https://issues.apache.org/jira/browse/IMPALA-6597
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 2.6.0
> Reporter: Istvan Szukacs
> Priority: Major
>
> I am not sure how to interpret the following:
> {code}
> WARNINGS:
> Memory limit exceeded
> Failed to allocate tuple buffer
> Memory Limit Exceeded
> HDFS_SCAN_NODE (id=1) could not allocate 1.42 MB without exceeding limit.
> Query(e44f072adac3070c:7cd293d8aa10b8a) Limit: Consumption=12.94 GB
> Fragment e44f072adac3070c:7cd293d8aa10b8e: Consumption=12.94 GB
> SORT_NODE (id=3): Consumption=12.77 GB
> UNION_NODE (id=0): Consumption=2.85 MB
> HDFS_SCAN_NODE (id=1): Consumption=174.29 MB
> HDFS_SCAN_NODE (id=2): Consumption=0
> DataStreamSender: Consumption=88.00 B
> Block Manager: Limit=10.51 GB Consumption=0
> Memory Limit Exceeded
> Query(e44f072adac3070c:7cd293d8aa10b8a) Limit: Consumption=12.79 GB
> Fragment e44f072adac3070c:7cd293d8aa10b8e: Consumption=12.79 GB
> SORT_NODE (id=3): Consumption=12.79 GB
> UNION_NODE (id=0): Consumption=8.00 KB
> HDFS_SCAN_NODE (id=1): Consumption=124.00 KB
> HDFS_SCAN_NODE (id=2): Consumption=0
> Block Manager: Limit=10.51 GB Consumption=0
> {code}
> mem_limit is configured to be 32GB. What configuration value can be tuned to
> have more memory for an Impala query?
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
