[ 
https://issues.apache.org/jira/browse/IMPALA-11968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17700898#comment-17700898
 ] 

Quanlong Huang commented on IMPALA-11968:
-----------------------------------------

Saw the same failure in 
https://jenkins.impala.io/job/ubuntu-16.04-from-scratch/18923/

It's due to the event-processor comes into ERROR state due to IMPALA-12002
{noformat}
E0315 17:54:14.959136  2659 MetastoreEventsProcessor.java:865] Unexpected 
exception received while processing event
Java exception follows:
org.apache.impala.catalog.events.MetastoreNotificationException: EventId: 26044 
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
E0315 17:54:14.959192  2659 MetastoreEventsProcessor.java:1040] Notification 
event is null
W0315 17:54:15.959450  2659 MetastoreEventsProcessor.java:844] Event processing 
is skipped since status is ERROR. Last synced event id is 26042{noformat}

> test_event_based_replication fails with timeout
> -----------------------------------------------
>
>                 Key: IMPALA-11968
>                 URL: https://issues.apache.org/jira/browse/IMPALA-11968
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Catalog
>            Reporter: Zoltán Borók-Nagy
>            Assignee: Quanlong Huang
>            Priority: Blocker
>              Labels: broken-build
>
> Might be related to IMPALA-11352 but the error message is a bit different.
> h3. Error Message
> {noformat}
> metadata/test_event_processing.py:179: in test_event_based_replication     
> self.__run_event_based_replication_tests() 
> metadata/test_event_processing.py:194: in __run_event_based_replication_tests 
>     EventProcessorUtils.wait_for_event_processing(self) 
> util/event_processor_utils.py:65: in wait_for_event_processing     within {1} 
> seconds".format(current_event_id, timeout)) E   Exception: Event processor 
> did not sync till last known event id 45924         within 10 seconds
> {noformat}
> h3. Stacktrace
> {noformat}
> metadata/test_event_processing.py:179: in test_event_based_replication
>     self.__run_event_based_replication_tests()
> metadata/test_event_processing.py:194: in __run_event_based_replication_tests
>     EventProcessorUtils.wait_for_event_processing(self)
> util/event_processor_utils.py:65: in wait_for_event_processing
>     within {1} seconds".format(current_event_id, timeout))
> E   Exception: Event processor did not sync till last known event id 45924    
>      within 10 seconds
> {noformat}
> h3. Standard Error
> {noformat}
> SET 
> client_identifier=metadata/test_event_processing.py::TestEventProcessing::()::test_event_based_replication;
> -- connecting to: localhost:21000
> -- 2023-03-02 05:46:47,066 INFO     MainThread: Could not connect to ('::1', 
> 21000, 0, 0)
> Traceback (most recent call last):
>   File 
> "/data/jenkins/workspace/impala-cdw-master-exhaustive/Impala-Toolchain/toolchain-packages-gcc10.4.0/thrift-0.11.0-p5/python/lib/python2.7/site-packages/thrift/transport/TSocket.py",
>  line 104, in open
>     handle.connect(sockaddr)
>   File 
> "/data/jenkins/workspace/impala-cdw-master-exhaustive/Impala-Toolchain/toolchain-packages-gcc10.4.0/python-2.7.16/lib/python2.7/socket.py",
>  line 228, in meth
>     return getattr(self._sock,name)(*args)
> error: [Errno 111] Connection refused
> -- connecting to localhost:21050 with impyla
> -- 2023-03-02 05:46:47,067 INFO     MainThread: Could not connect to ('::1', 
> 21050, 0, 0)
> Traceback (most recent call last):
>   File 
> "/data/jenkins/workspace/impala-cdw-master-exhaustive/Impala-Toolchain/toolchain-packages-gcc10.4.0/thrift-0.11.0-p5/python/lib/python2.7/site-packages/thrift/transport/TSocket.py",
>  line 104, in open
>     handle.connect(sockaddr)
>   File 
> "/data/jenkins/workspace/impala-cdw-master-exhaustive/Impala-Toolchain/toolchain-packages-gcc10.4.0/python-2.7.16/lib/python2.7/socket.py",
>  line 228, in meth
>     return getattr(self._sock,name)(*args)
> error: [Errno 111] Connection refused
> -- 2023-03-02 05:46:47,077 INFO     MainThread: Closing active operation
> -- connecting to localhost:28000 with impyla
> -- 2023-03-02 05:46:47,089 INFO     MainThread: Closing active operation
> -- connecting to localhost:11050 with impyla
> -- 2023-03-02 05:46:52,124 INFO     MainThread: Waiting until events 
> processor syncs to event id:45924
> {noformat}
>  



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to