You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Quanlong Huang (Jira)" <ji...@apache.org> on 2020/10/27 02:05:00 UTC
[jira] [Assigned] (IMPALA-10280)
TestConcurrentDdls.test_concurrent_invalidate_metadata hits INVALIDATE
METADATA timeout on s3
[ https://issues.apache.org/jira/browse/IMPALA-10280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Quanlong Huang reassigned IMPALA-10280:
---------------------------------------
Assignee: Quanlong Huang
> TestConcurrentDdls.test_concurrent_invalidate_metadata hits INVALIDATE METADATA timeout on s3
> ---------------------------------------------------------------------------------------------
>
> Key: IMPALA-10280
> URL: https://issues.apache.org/jira/browse/IMPALA-10280
> Project: IMPALA
> Issue Type: Bug
> Components: Frontend
> Affects Versions: Impala 4.0
> Reporter: Joe McDonnell
> Assignee: Quanlong Huang
> Priority: Critical
> Labels: broken-build, flaky
>
> A recent test run on s3 hit the following test failure:
> {noformat}
> custom_cluster/test_concurrent_ddls.py:194: in test_concurrent_invalidate_metadata
> assert False, "INVALIDATE METADATA timeout in 60s!"
> E AssertionError: INVALIDATE METADATA timeout in 60s!
> E assert False{noformat}
> This seems to be distinct from IMPALA-10077, as this is an actual timeout on the INVALIDATE METADATA, not the test as a whole.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org