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 2023/03/15 02:30:00 UTC

[jira] [Created] (IMPALA-12002) COMMIT_COMPACTION_EVENT are not correctly skipped if the db not found

Quanlong Huang created IMPALA-12002:
---------------------------------------

             Summary: COMMIT_COMPACTION_EVENT are not correctly skipped if the db not found
                 Key: IMPALA-12002
                 URL: https://issues.apache.org/jira/browse/IMPALA-12002
             Project: IMPALA
          Issue Type: Bug
            Reporter: Quanlong Huang
            Assignee: Sai Hemanth Gantasala


I saw event-processor is stopped due to an error in a CORE build:
{code}
I0313 02:30:30.313375 30039 MetastoreEventsProcessor.java:805] Received 8 events. Start event id : 26504
I0313 02:30:30.313757 30039 MetastoreEventsProcessor.java:1026] Time elapsed in processing event batch: 283.896us
E0313 02:30:30.313935 30039 MetastoreEventsProcessor.java:865] Unexpected exception received while processing event
Java exception follows:
org.apache.impala.catalog.events.MetastoreNotificationException: EventId: 26506 EventType: COMMIT_COMPACTION_EVENT Unable to parse commit compaction message
        at org.apache.impala.catalog.events.MetastoreEvents$CommitCompactionEvent.<init>(MetastoreEvents.java:2684)
        at org.apache.impala.catalog.events.MetastoreEvents$MetastoreEventFactory.get(MetastoreEvents.java:223)
        at org.apache.impala.catalog.events.MetastoreEvents$MetastoreEventFactory.getFilteredEvents(MetastoreEvents.java:255)
        at org.apache.impala.catalog.events.MetastoreEventsProcessor.processEvents(MetastoreEventsProcessor.java:999)
        at org.apache.impala.catalog.events.MetastoreEventsProcessor.processEvents(MetastoreEventsProcessor.java:851)
        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:748)
Caused by: org.apache.impala.catalog.DatabaseNotFoundException: Database 'test_acid_compaction_5c682e9f' not found
        at org.apache.impala.catalog.Catalog.getTable(Catalog.java:196)
        at org.apache.impala.catalog.events.MetastoreEvents$CommitCompactionEvent.<init>(MetastoreEvents.java:2679)
        ... 11 more
E0313 02:30:30.314000 30039 MetastoreEventsProcessor.java:1040] Notification event is null
W0313 02:30:31.314235 30039 MetastoreEventsProcessor.java:844] Event processing is skipped since status is ERROR. Last synced event id is 26504
{code}
"test_acid_compaction_5c682e9f" is a temp db created by tests. It's already dropped when catalogd received the commit compaction event. The exception is thrown from the constructor of CommitCompactionEvent. We should skip the event instead of let it fails the event-processor.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)