Jonathan Vexler created HUDI-8701:
-------------------------------------
Summary: Lock Metrics can fail during unlock even though lock does
not fail
Key: HUDI-8701
URL: https://issues.apache.org/jira/browse/HUDI-8701
Project: Apache Hudi
Issue Type: Bug
Reporter: Jonathan Vexler
Assignee: Jonathan Vexler
stacktrace:
{code:java}
java.util.concurrent.CompletionException:
org.apache.hudi.exception.HoodieException: Timer was not started at
java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:273)
at
java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:280)
at
java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1643)
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:750)Caused by:
org.apache.hudi.exception.HoodieException: Timer was not started at
org.apache.hudi.common.util.HoodieTimer.endTimer(HoodieTimer.java:81) at
org.apache.hudi.client.transaction.lock.metrics.HoodieLockMetrics.updateLockHeldTimerMetrics(HoodieLockMetrics.java:113)
at
org.apache.hudi.client.transaction.lock.LockManager.unlock(LockManager.java:110)
at
org.apache.hudi.client.transaction.TransactionManager.endTransaction(TransactionManager.java:69)
at
org.apache.hudi.client.BaseHoodieTableServiceClient.scheduleTableService(BaseHoodieTableServiceClient.java:624)
at
org.apache.hudi.client.BaseHoodieWriteClient.scheduleTableService(BaseHoodieWriteClient.java:1296)
at
org.apache.hudi.client.BaseHoodieWriteClient.scheduleCompactionAtInstant(BaseHoodieWriteClient.java:1048)
at
org.apache.hudi.client.BaseHoodieWriteClient.scheduleCompaction(BaseHoodieWriteClient.java:1039)
{code}
Metric failure should not be cause of total failure. We should warn and recover
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
