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

Csaba Ringhofer commented on IMPALA-14118:
------------------------------------------

[~VenuReddy] I just saw this in a test, don't know how frequent the issue is.

> test_perf_hive_transact_part_table_hierarchical is flaky
> --------------------------------------------------------
>
>                 Key: IMPALA-14118
>                 URL: https://issues.apache.org/jira/browse/IMPALA-14118
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Catalog
>            Reporter: Csaba Ringhofer
>            Priority: Critical
>
> Saw this in an exhaustive release ARM build:
> {code}
> custom_cluster/test_event_processing_perf.py:164: in 
> test_perf_hive_transact_part_table_hierarchical
>     True, True, True)
> custom_cluster/test_event_processing_perf.py:380: in 
> __run_event_processing_tests
>     insert_into_part_time = self.__process_events(start_event_id)
> custom_cluster/test_event_processing_perf.py:489: in __process_events
>     return self.__process_events_now(start_event_id)
> custom_cluster/test_event_processing_perf.py:484: in __process_events_now
>     self.__ensure_events_processed()
> custom_cluster/test_event_processing_perf.py:493: in __ensure_events_processed
>     EventProcessorUtils.wait_for_event_processing(self, 100)
> util/event_processor_utils.py:95: in wait_for_event_processing
>     impala_cluster, timeout, error_status_possible)
> util/event_processor_utils.py:109: in wait_for_event_processing_impl
>     current_event_id)
> util/event_processor_utils.py:69: in wait_for_synced_event_id
>     .format(status, error_msg))
> E   Exception: Event processor is not working. Status: ERROR. Error msg: 
> 2025-05-30T08:06:31.782
> E   Unexpected exception received while processing event
> E   java.lang.IllegalStateException: outstandingEventCount is negative after 
> decrement.
> E     at 
> com.google.common.base.Preconditions.checkState(Preconditions.java:512)
> E     at 
> org.apache.impala.catalog.events.DbEventExecutor.decrOutstandingEventCount(DbEventExecutor.java:464)
> E     at 
> org.apache.impala.catalog.events.DbEventExecutor.access$300(DbEventExecutor.java:76)
> E     at 
> org.apache.impala.catalog.events.DbEventExecutor$DbProcessor.process(DbEventExecutor.java:395)
> E     at 
> org.apache.impala.catalog.events.DbEventExecutor$DbProcessor.access$1200(DbEventExecutor.java:119)
> E     at 
> org.apache.impala.catalog.events.DbEventExecutor.process(DbEventExecutor.java:633)
> E     at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> E     at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> E     at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> E     at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> E     at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> E     at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> E     at java.lang.Thread.run(Thread.java:750)
> E   
> E   Notification event is null
> {code}



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org

Reply via email to