[
https://issues.apache.org/jira/browse/IMPALA-6382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bikramjeet Vig resolved IMPALA-6382.
------------------------------------
Resolution: Fixed
Fix Version/s: Impala 2.12.0
[https://github.com/apache/impala/commit/028a83e6543a18dd3b9161226355f1e8d36c4ed7]
IMPALA-6382: Cap spillable buffer size and max row size query options
Currently the default and min spillable buffer size and max row size query
options accept any valid int64 value. Since the planner depends on these values
for memory estimations, if a very large value close to the limits of int64 is
set, the variables representing or relying on these estimates can overflow
during different phases of query execution. This patch puts a reasonable upper
limit of 1TB to these query options to prevent such a situation. Testing: Added
backend query option tests. Change-Id:
I36d3915f7019b13c3eb06f08bfdb38c71ec864f1 Reviewed-on:
[http://gerrit.cloudera.org:8080/9023]Reviewed-by: Bikramjeet Vig
<bikramjeet....@cloudera.com> Tested-by: Impala Public Jenkins
> Impalad crashes on SELECT query when spill buffer is set on certain values
> --------------------------------------------------------------------------
>
> Key: IMPALA-6382
> URL: https://issues.apache.org/jira/browse/IMPALA-6382
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 2.10.0, Impala 2.11.0, Impala 2.12.0
> Environment: Impala mini cluster
> Reporter: Xinran Tinney
> Assignee: Bikramjeet Vig
> Priority: Critical
> Labels: crash
> Fix For: Impala 2.12.0
>
> Attachments: Nocrashwithdifferentbuffersize.png,
> impalacrashesonbigbuffersize.png
>
>
> After starting the minicluster and run bin/impala-shell.sh, do
> set MIN_SPILLABLE_BUFFER_SIZE= 4611686018427387904;
> set DEFAULT_SPILLABLE_BUFFER_SIZE=4611686018427387904;
> use tpch;
> select distinct l_comment from lineitem;
> then impalad is crashed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
