[ 
https://issues.apache.org/jira/browse/IMPALA-15265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18106809#comment-18106809
 ] 

ASF subversion and git services commented on IMPALA-15265:
----------------------------------------------------------

Commit 5dc944e13c8ff3aaa3b0c75ff45416ebe9c5e4e2 in impala's branch 
refs/heads/master from Joe McDonnell
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=5dc944e13 ]

IMPALA-15265: Fix internal-server-test's long execution time

After the default file format changed to Parquet, the
internal-server-test's QueryTimeout has been taking
35+ minutes to run. The test runs a SQL with a predicate
"where id=sleep(2000000)" and FETCH_ROWS_TIMEOUT_MS=1.
The idea is that the sleep happens during execution and
we hit the timeout. With the switch to Parquet, the
logic for Parquet dictionary filtering is evaluating
the predicate at planning time to determine if it
returns true for NULL. This causes it to sleep for
35+ minutes, and the FETCH_ROWS_TIMEOUT_MS doesn't
kick in.

This turns off Parquet dictionary filtering for this
test, which avoids the sleep during planning. It also
adds a check of the time that the test runs to verify
that it runs in less than a minute.

Testing:
 - Ran test locally

Change-Id: I6b960aecb4bf50395fc64ed8263b02b6b92180d2
Reviewed-on: http://gerrit.cloudera.org:8080/24720
Reviewed-by: Michael Smith <[email protected]>
Tested-by: Michael Smith <[email protected]>


> internal-server-test slowed down considerably and now takes 30+ minutes
> -----------------------------------------------------------------------
>
>                 Key: IMPALA-15265
>                 URL: https://issues.apache.org/jira/browse/IMPALA-15265
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>    Affects Versions: Impala 5.0.0
>            Reporter: Joe McDonnell
>            Priority: Critical
>             Fix For: Impala 5.0.0
>
>
> internal-server-test is taking a long long time now (35+ minutes):
> {noformat}
> 04:42:28         Start  90: internal-server-test
> 05:18:15  90/166 Test  #90: internal-server-test ...................   Passed 
>  2146.37 sec{noformat}
> It used to run much faster (2.5 minutes):
> {noformat}
> 19:55:00         Start  89: internal-server-test
> 19:57:26  89/164 Test  #89: internal-server-test ...................   Passed 
>  146.09 sec{noformat}
> We should figure out what happened and when. This is relatively recent.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to