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 "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/04/28 23:43:00 UTC
[jira] [Commented] (IMPALA-6560) Come up with reliable regression
test for IMPALA-2376
[ https://issues.apache.org/jira/browse/IMPALA-6560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16457849#comment-16457849 ]
ASF subversion and git services commented on IMPALA-6560:
---------------------------------------------------------
Commit 93d714c6458a680151c7208b1fe23677f4705a17 in impala's branch refs/heads/master from [~tarmstrong@cloudera.com]
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=93d714c ]
IMPALA-6560: fix regression test for IMPALA-2376
The test is modified to increase the size of collections allocated.
num_nodes and mt_dop query options are set to make execution as
deterministic as possible.
I looped the test overnight to try to flush out flakiness.
Adds support for row_regex lines in CATCH sections so that we can
match a larger part of the error message.
Change-Id: I024cb6b57647902b1735defb885cd095fd99738c
Reviewed-on: http://gerrit.cloudera.org:8080/9681
Reviewed-by: Tim Armstrong <ta...@cloudera.com>
Tested-by: Tim Armstrong <ta...@cloudera.com>
> Come up with reliable regression test for IMPALA-2376
> -----------------------------------------------------
>
> Key: IMPALA-6560
> URL: https://issues.apache.org/jira/browse/IMPALA-6560
> Project: IMPALA
> Issue Type: Test
> Components: Backend
> Reporter: Tim Armstrong
> Assignee: Tim Armstrong
> Priority: Major
> Labels: resource-management
>
> We don't have a good regression test for IMPALA-2376. With IMPALA-4835 and other changes it's increasingly difficult to get the query to OOM at the intended place. We probably need to construct some special test data with a very large nested collection to trigger this bug.
> This is based on the TODO:
> {noformat}
> ====
> ---- QUERY
> # IMPALA-2376
> # Set memory limit low enough to get the below query to consistently fail.
> # TODO: change query and/or table so we can consistently check for the following error:
> # Failed to allocate buffer for collection '...'.
> set mem_limit=4m;
> select max(cnt) from customer c,
> (select count(l_returnflag) cnt from c.c_orders.o_lineitems) v;
> ---- TYPES
> BIGINT
> ---- CATCH
> Memory limit exceeded
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org