[
https://issues.apache.org/jira/browse/IMPALA-14618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18044049#comment-18044049
]
Quanlong Huang commented on IMPALA-14618:
-----------------------------------------
It seems the CREATE_TABLE event is missed in the standby catalogd when it
becomes active. So the table is missing in the new active catalogd.
{noformat}
I20251207 11:45:45.311270 2338302 MetastoreEvents.java:947] EventId: 61211
EventType: CREATE_TABLE Target:
test_failover_catchup_timeout_and_reset_5d02c505.tbl. Enqueued for db:
test_failover_catchup_timeout_and_reset_5d02c505 on executor: DbEventExecutor-0
I20251207 11:45:45.311333 2338302 MetastoreEvents.java:947] EventId: 61211
EventType: CREATE_TABLE Target:
test_failover_catchup_timeout_and_reset_5d02c505.tbl. Dispatch time: 5ms
...
I20251207 11:45:47.925884 2338234 DbEventExecutor.java:386] Processor is
terminating for db: test_failover_catchup_timeout_and_reset_5d02c505. Caller
stacktrace:
org.apache.impala.catalog.events.DbEventExecutor$DbProcessor.isTerminating(DbEventExecutor.java:387)
at
org.apache.impala.catalog.events.DbEventExecutor$DbProcessor.processDbEvents(DbEventExecutor.java:322)
at
org.apache.impala.catalog.events.DbEventExecutor$DbProcessor.process(DbEventExecutor.java:468)
at
org.apache.impala.catalog.events.DbEventExecutor$DbProcessor.access$1200(DbEventExecutor.java:119)
at
org.apache.impala.catalog.events.DbEventExecutor.process(DbEventExecutor.java:696)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:750){noformat}
Assigning this to [~VenuReddy] since this seems to be an issue of hierarchical
event processing.
> TestCatalogdHA.test_failover_catchup_timeout_and_reset failing
> --------------------------------------------------------------
>
> Key: IMPALA-14618
> URL: https://issues.apache.org/jira/browse/IMPALA-14618
> Project: IMPALA
> Issue Type: Bug
> Reporter: Surya Hebbar
> Assignee: Quanlong Huang
> Priority: Major
> Attachments:
> catalogd.impala-ec2-redhat86-m6i-4xlarge-ondemand-1ce4.vpc.cloudera.com.jenkins.log.INFO.20251207-114532.2336954,
>
> catalogd.impala-ec2-redhat86-m6i-4xlarge-ondemand-1ce4.vpc.cloudera.com.jenkins.log.INFO.20251207-114532.2336965,
>
> impalad.impala-ec2-redhat86-m6i-4xlarge-ondemand-1ce4.vpc.cloudera.com.jenkins.log.INFO.20251207-114532.2337035
>
>
> h3. Error Message
> {code}
> assert '26000' in "Query 294e9bcf7bfb219a:72be327b00000000
> failed:\nAnalysisException: Could not resolve path:
> 'test_failover_catchup_timeout_and_reset_5d02c505.tbl'\n\n" + where '26000'
> = str(26000) + where 26000 = <tests.common.impala_service.CatalogdService
> object at 0x7f51b29a3520>.service_port + where
> <tests.common.impala_service.CatalogdService object at 0x7f51b29a3520> =
> <CatalogdProcess PID: None
> (/data/jenkins/workspace/impala-asf-master-core-ozone/repos/Impala/be/build/latest/service/...ist.txt
> -catalog_service_port=26000 -state_store_subscriber_port=23020
> -webserver_port=25020 -enable_catalogd_ha=true)>.service + and "Query
> 294e9bcf7bfb219a:72be327b00000000 failed:\nAnalysisException: Could not
> resolve path: 'test_failover_catchup_timeout_and_reset_5d02c505.tbl'\n\n" =
> str(HiveServer2Error("Query 294e9bcf7bfb219a:72be327b00000000
> failed:\nAnalysisException: Could not resolve path:
> 'test_failover_catchup_timeout_and_reset_5d02c505.tbl'\n\n"))
> {code}
> h3. Stacktrace
> {code}
> custom_cluster/test_catalogd_ha.py:608: in
> test_failover_catchup_timeout_and_reset
> self._test_metadata_after_failover(
> custom_cluster/test_catalogd_ha.py:787: in _test_metadata_after_failover
> assert str(active_catalogd.service.service_port) in str(e)
> E assert '26000' in "Query 294e9bcf7bfb219a:72be327b00000000
> failed:\nAnalysisException: Could not resolve path:
> 'test_failover_catchup_timeout_and_reset_5d02c505.tbl'\n\n"
> E + where '26000' = str(26000)
> E + where 26000 = <tests.common.impala_service.CatalogdService object
> at 0x7f51b29a3520>.service_port
> E + where <tests.common.impala_service.CatalogdService object at
> 0x7f51b29a3520> = <CatalogdProcess PID: None
> (/data/jenkins/workspace/impala-asf-master-core-ozone/repos/Impala/be/build/latest/service/...ist.txt
> -catalog_service_port=26000 -state_store_subscriber_port=23020
> -webserver_port=25020 -enable_catalogd_ha=true)>.service
> E + and "Query 294e9bcf7bfb219a:72be327b00000000
> failed:\nAnalysisException: Could not resolve path:
> 'test_failover_catchup_timeout_and_reset_5d02c505.tbl'\n\n" =
> str(HiveServer2Error("Query 294e9bcf7bfb219a:72be327b00000000
> failed:\nAnalysisException: Could not resolve path:
> 'test_failover_catchup_timeout_and_reset_5d02c505.tbl'\n\n"))
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
