[
https://issues.apache.org/jira/browse/IMPALA-8118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16752510#comment-16752510
]
Tim Armstrong commented on IMPALA-8118:
---------------------------------------
Not sure if the query that logged the memory limit error is the one that
crashed, but
{noformat}
I0125 05:25:14.304028 41419 Frontend.java:1242]
974ec7e179ce3698:6f26a17d00000000] Analyzing query: select
c_name,
c_custkey,
o_orderkey,
o_orderdate,
o_totalprice,
sum(l_quantity)
from
customer,
orders,
lineitem
where
o_orderkey in (
select
l_orderkey
from
lineitem
group by
l_orderkey
having
sum(l_quantity) > 300
)
and c_custkey = o_custkey
and o_orderkey = l_orderkey
group by
c_name,
c_custkey,
o_orderkey,
o_orderdate,
o_totalprice
order by
o_totalprice desc,
o_orderdate,
o_orderkey
limit 100
{noformat}
{noformat}
74: client_identifier (string) =
"query_test/test_mem_usage_scaling.py::TestTpchMemLimitError::()::test_low_mem_limit_q18[mem_limit:130|protocol:beeswax|exec_option:{'batch_size':0;'num_nodes':0;'disable_codegen_rows_threshold':0;'disable_codegen':False;'abort_on_error':1;'exec_single_nod",
{noformat}
But I think that query might have actually completed and be unrelated to the
crash.
> Build failure: Connection failure in multiple tests
> ---------------------------------------------------
>
> Key: IMPALA-8118
> URL: https://issues.apache.org/jira/browse/IMPALA-8118
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 3.1.0
> Reporter: Paul Rogers
> Assignee: Lenisha Gandhi
> Priority: Blocker
> Fix For: Impala 3.1.0
>
>
> Build of latest master, with ASAN, failed with the following error, which to
> my newbie eyes looks like a connection failure:
> {noformat}
> 05:42:04 =================================== FAILURES
> ===================================
> 05:42:04 TestQueriesTextTables.test_data_source_tables[protocol: beeswax |
> exec_option: {'batch_size': 0, 'num_nodes': 0,
> 'disable_codegen_rows_threshold': 0, 'disable_codegen': False,
> 'abort_on_error': 1, 'exec_single_node_rows_threshold': 0} | table_format:
> text/none]
> 05:42:04 [gw5] linux2 -- Python 2.7.5
> /data/jenkins/workspace/impala-cdh6.x-core-asan/repos/Impala/bin/../infra/python/env/bin/python
> 05:42:04 query_test/test_queries.py:174: in test_data_source_tables
> 05:42:04 self.run_test_case('QueryTest/data-source-tables', vector)
> 05:42:04 common/impala_test_suite.py:472: in run_test_case
> 05:42:04 result = self.__execute_query(target_impalad_client, query,
> user=user)
> ...
> 05:42:04 handle = self.execute_query_async(query_string, user=user)
> 05:42:04 beeswax/impala_beeswax.py:351: in execute_query_async
> 05:42:04 handle = self.__do_rpc(lambda: self.imp_service.query(query,))
> 05:42:04 beeswax/impala_beeswax.py:512: in __do_rpc
> 05:42:04 raise ImpalaBeeswaxException(self.__build_error_message(e), e)
> 05:42:04 E ImpalaBeeswaxException: ImpalaBeeswaxException:
> 05:42:04 E INNER EXCEPTION: <class
> 'thrift.transport.TTransport.TTransportException'>
> 05:42:04 E MESSAGE: TSocket read 0 bytes
> 05:42:04 ----------------------------- Captured stderr call
> -----------------------------
> ...
> 05:42:04 -- executing against localhost:21000
> 05:42:04 select *
> 05:42:04 from alltypes_datasource
> 05:42:04 where float_col != 0 and
> 05:42:04 int_col >= 1990 limit 5;
> {noformat}
> A similar error appears for multiple other tests. Then:
> {noformat}
> 05:42:04 TTransportException: Could not connect to localhost:21050
> 05:42:04 !!!!!!!!!!!!!!!!!!! Interrupted: stopping after 10 failures
> !!!!!!!!!!!!!!!!!!!!
> {noformat}
> I wonder if these are just symptoms of a failure in the BE code due to ASAN
> being enabled.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]