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

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

Commit b97c9e796689dc114fd8f1ceaf037f1364242ce3 in impala's branch 
refs/heads/master from Bikramjeet Vig
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=b97c9e7 ]

IMPALA-8202: Extend query timeout for test_mem_limit

With the current timeout set to 1 sec, we saw flaky failure where
the query timed out due to client inactivity. This can happen if
the thread keeping it alive fails to execute a fetch within the
query timeout period. This patch attempts to fix this flakiness
by increasing the timeout period.

Testing:
Looped the test locally.

Change-Id: Ic02f73bea528af12053043e0a57b4158532833b4
Reviewed-on: http://gerrit.cloudera.org:8080/16774
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>


> TestAdmissionControllerStress.test_mem_limit teardown() fails with "Invalid 
> or unknown query handle"
> ----------------------------------------------------------------------------------------------------
>
>                 Key: IMPALA-8202
>                 URL: https://issues.apache.org/jira/browse/IMPALA-8202
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>    Affects Versions: Impala 3.2.0
>            Reporter: Andrew Sherman
>            Assignee: Bikramjeet Vig
>            Priority: Critical
>              Labels: broken-build
>
> teardown() attempts to close each submission thread that was used. But one of 
> them times out.
> {quote}
> 06:05:22  ERROR at teardown of 
> TestAdmissionControllerStress.test_mem_limit[num_queries: 50 | protocol: 
> beeswax | table_format: text/none | exec_option: {'batch_size': 0, 
> 'num_nodes': 0, 'disable_codegen_rows_threshold': 5000, 'disable_codegen': 
> False, 'abort_on_error': 1, 'exec_single_node_rows_threshold': 0} | 
> submission_delay_ms: 50 | round_robin_submission: True] 
> 06:05:22 custom_cluster/test_admission_controller.py:1004: in teardown
> 06:05:22     client.cancel(thread.query_handle)
> 06:05:22 common/impala_connection.py:183: in cancel
> 06:05:22     return 
> self.__beeswax_client.cancel_query(operation_handle.get_handle())
> 06:05:22 beeswax/impala_beeswax.py:364: in cancel_query
> 06:05:22     return self.__do_rpc(lambda: self.imp_service.Cancel(query_id))
> 06:05:22 beeswax/impala_beeswax.py:512: in __do_rpc
> 06:05:22     raise ImpalaBeeswaxException(self.__build_error_message(b), b)
> 06:05:22 E   ImpalaBeeswaxException: ImpalaBeeswaxException:
> 06:05:22 E    INNER EXCEPTION: <class 'beeswaxd.ttypes.BeeswaxException'>
> 06:05:22 E    MESSAGE: Invalid or unknown query handle
> {quote}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to