George Huang created HDDS-7934:
----------------------------------

             Summary: java.lang.NullPointerException: at 
org.apache.hadoop.ozone.util.ShutdownHookManager.executeShutdown(ShutdownHookManager.java:132)
                 Key: HDDS-7934
                 URL: https://issues.apache.org/jira/browse/HDDS-7934
             Project: Apache Ozone
          Issue Type: Bug
          Components: freon
            Reporter: George Huang


 
{code:java}
***************************************************
Status: Success
Git Base Revision: 39dba86fbcf282ba02f5c32e6e2246cf98ff2cdf
Number of Volumes created: 3
Number of Buckets created: 30
Number of Keys added: 900
23/02/08 13:57:09 WARN util.ShutdownHookManager: ShutdownHook 
'RandomKeyGenerator$$Lambda$52/1000171161' failed, 
java.util.concurrent.ExecutionException: java.lang.NullPointerException
java.util.concurrent.ExecutionException: java.lang.NullPointerException
 at java.util.concurrent.FutureTask.report(FutureTask.java:122)
 at java.util.concurrent.FutureTask.get(FutureTask.java:206)
 at 
org.apache.hadoop.ozone.util.ShutdownHookManager.executeShutdown(ShutdownHookManager.java:132)
 at 
org.apache.hadoop.ozone.util.ShutdownHookManager$1.run(ShutdownHookManager.java:103)
Caused by: java.lang.NullPointerException
 at 
org.apache.hadoop.ozone.freon.RandomKeyGenerator.printStats(RandomKeyGenerator.java:487)
 at 
org.apache.hadoop.ozone.freon.RandomKeyGenerator.lambda$addShutdownHook$0(RandomKeyGenerator.java:399)
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
 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)
{code}
 



--
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