You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Quanlong Huang (Jira)" <ji...@apache.org> on 2020/02/08 00:02:00 UTC
[jira] [Resolved] (IMPALA-9159) test_concurrent_ddls.py's
test_ddls_with_invalidate_metadata_sync_ddl timed out after 17 hours
[ https://issues.apache.org/jira/browse/IMPALA-9159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Quanlong Huang resolved IMPALA-9159.
------------------------------------
Fix Version/s: Impala 3.4.0
Resolution: Fixed
Haven't seen this after IMPALA-9211. Resolve this and feel free to reopen it if it happends again.
> test_concurrent_ddls.py's test_ddls_with_invalidate_metadata_sync_ddl timed out after 17 hours
> ----------------------------------------------------------------------------------------------
>
> Key: IMPALA-9159
> URL: https://issues.apache.org/jira/browse/IMPALA-9159
> Project: IMPALA
> Issue Type: Bug
> Components: Frontend
> Affects Versions: Impala 3.4.0
> Reporter: Joe McDonnell
> Assignee: Quanlong Huang
> Priority: Critical
> Labels: broken-build
> Fix For: Impala 3.4.0
>
> Attachments: stderr.out
>
>
> One run of test_concurrent_ddls.TestConcurrentDdls.test_ddls_with_invalidate_metadata_sync_ddl on erasure coding got stuck for 17 hours:
> {noformat}
> 20:03:55 custom_cluster/test_concurrent_ddls.py::TestConcurrentDdls::test_ddls_with_invalidate_metadata PASSED
> 13:18:50 custom_cluster/test_concurrent_ddls.py::TestConcurrentDdls::test_ddls_with_invalidate_metadata_sync_ddl
> 13:18:50
> 13:18:50 **** Tests TIMED OUT! ****{noformat}
> I will attach some of the logs produced. The failure just shows Impala getting killed because the test timed out:
> {noformat}
> conftest.py:337: in cleanup
> request.instance.execute_query_expect_success(request.instance.client, "use default")
> common/impala_test_suite.py:801: in wrapper
> return function(*args, **kwargs)
> common/impala_test_suite.py:809: in execute_query_expect_success
> result = cls.__execute_query(impalad_client, query, query_options, user)
> common/impala_test_suite.py:904: in __execute_query
> return impalad_client.execute(query, user=user)
> common/impala_connection.py:205: in execute
> return self.__beeswax_client.execute(sql_stmt, user=user)
> beeswax/impala_beeswax.py:187: in execute
> handle = self.__execute_query(query_string.strip(), user=user)
> beeswax/impala_beeswax.py:362: in __execute_query
> handle = self.execute_query_async(query_string, user=user)
> beeswax/impala_beeswax.py:356: in execute_query_async
> handle = self.__do_rpc(lambda: self.imp_service.query(query,))
> beeswax/impala_beeswax.py:522: in __do_rpc
> raise ImpalaBeeswaxException(self.__build_error_message(e), e)
> E ImpalaBeeswaxException: ImpalaBeeswaxException:
> E INNER EXCEPTION: <class 'thrift.transport.TTransport.TTransportException'>
> E MESSAGE: TSocket read 0 bytes{noformat}
> As far as I can tell, this has been seen once and that occurrence was on the erasure coding configuration.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)