Fang-Yu Rao created IMPALA-10363:
------------------------------------
Summary: test_mixed_catalog_ddls_with_invalidate_metadata failed
after reaching timeout (120 seconds)
Key: IMPALA-10363
URL: https://issues.apache.org/jira/browse/IMPALA-10363
Project: IMPALA
Issue Type: Bug
Reporter: Fang-Yu Rao
Assignee: Quanlong Huang
Fix For: Impala 4.0
Attachments:
catalogd.impala-ec2-centos74-m5-4xlarge-ondemand-1357.vpc.cloudera.com.jenkins.log.INFO.20201127-081551.13559,
consoleFull_impala-cdpd-master-staging-core-s3.txt,
impalad.impala-ec2-centos74-m5-4xlarge-ondemand-1357.vpc.cloudera.com.jenkins.log.INFO.20201127-081551.13631,
statestored.impala-ec2-centos74-m5-4xlarge-ondemand-1357.vpc.cloudera.com.jenkins.log.INFO.20201127-081551.13543
We found in an s3 run that the E2E test
{{test_mixed_catalog_ddls_with_invalidate_metadata}} at
https://github.com/apache/impala/blob/6539c50f6611d9e2ba9c3051b8e4c8bd6e79d1e1/tests/custom_cluster/test_concurrent_ddls.py#L58-L59
could fail after reaching timeout of 120 seconds with the following error
message.
{noformat}
Error Message
Failed: Timeout >120.0s
Stacktrace
custom_cluster/test_concurrent_ddls.py:59: in
test_mixed_catalog_ddls_with_invalidate_metadata
self._run_ddls_with_invalidation(unique_database, sync_ddl=False)
custom_cluster/test_concurrent_ddls.py:146: in _run_ddls_with_invalidation
for i in pool.imap_unordered(run_ddls, xrange(1, NUM_ITERS + 1)):
/usr/lib64/python2.7/multiprocessing/pool.py:642: in next
self._cond.wait(timeout)
/usr/lib64/python2.7/threading.py:339: in wait
waiter.acquire()
E Failed: Timeout >120.0s
{noformat}
{noformat}
Error Message
Failed: Timeout >120.0s
Stacktrace
custom_cluster/test_concurrent_ddls.py:59: in
test_mixed_catalog_ddls_with_invalidate_metadata
self._run_ddls_with_invalidation(unique_database, sync_ddl=False)
custom_cluster/test_concurrent_ddls.py:146: in _run_ddls_with_invalidation
for i in pool.imap_unordered(run_ddls, xrange(1, NUM_ITERS + 1)):
/usr/lib64/python2.7/multiprocessing/pool.py:642: in next
self._cond.wait(timeout)
/usr/lib64/python2.7/threading.py:339: in wait
waiter.acquire()
E Failed: Timeout >120.0s
{noformat}
Based on the following two lines in the console output of the Jenkins job, it
looks like the query id of the failed query is
{noformat}
08:20:05
custom_cluster/test_concurrent_ddls.py::TestConcurrentDdls::test_mixed_catalog_ddls_with_invalidate_metadata
-- 2020-11-27 08:20:05,777 INFO Thread-85: Started query
4b4d32c23dedf060:21e898dd00000000
08:21:14 FAILED
{noformat}
It looks like there were multiple queries being executed during this test. In
this regard, I provide the corresponding log files generated when the test was
executed. Let me know if other log files are needed as well. Thanks!
This test was recently added in IMPALA-7506. Maybe Quanlong could provide some
insight into it.
This JIRA may also be related to IMPALA-10301.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
