[ https://issues.apache.org/jira/browse/IMPALA-11644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Quanlong Huang resolved IMPALA-11644. ------------------------------------- Fix Version/s: Impala 4.2.0 Resolution: Fixed > updateLatestEventId should handle cases of empty events > ------------------------------------------------------- > > Key: IMPALA-11644 > URL: https://issues.apache.org/jira/browse/IMPALA-11644 > Project: IMPALA > Issue Type: Bug > Components: Catalog > Affects Versions: Impala 4.2.0 > Reporter: Quanlong Huang > Assignee: Quanlong Huang > Priority: Major > Fix For: Impala 4.2.0 > > > IMPALA-11490 adds a catalog metrics of latest event id in HMS. The retention > duration of notification events is 24 hours by default. If they are cleaned > up and there are no more events, the thread for updating latest event id will > encounter the following exception: > {noformat} > E1009 09:29:13.774916 11395 MetastoreEventsProcessor.java:898] Unable to > update current notification event id. Last value: -1 > Java exception follows: > java.util.NoSuchElementException > at java.util.ArrayList$Itr.next(ArrayList.java:864) > at > org.apache.impala.catalog.events.MetastoreEventsProcessor.updateLatestEventId(MetastoreEventsProcessor.java:891) > 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) {noformat} -- This message was sent by Atlassian Jira (v8.20.10#820010)