[IMPALA-11644] updateLatestEventId should handle cases of empty events

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Impala 4.2.0
• Fix Version/s: Impala 4.2.0
• Component/s: Catalog
• Epic Color: ghx-label-13
• Assignee: Quanlong Huang
• Reporter: Quanlong Huang
• Created: 09/Oct/22 01:37
• Updated: 12/Oct/22 05:17
• Resolved: 12/Oct/22 05:17

Description

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:

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)