rickyma opened a new issue, #1542:
URL: https://github.com/apache/incubator-uniffle/issues/1542

   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   
   
   ### Search before asking
   
   - [X] I have searched in the 
[issues](https://github.com/apache/incubator-uniffle/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### Describe the bug
   
   As described in https://github.com/apache/incubator-uniffle/pull/1537, here 
is the stack trace:
   
   [2024-02-24 21:01:20.540] [checkResource-0] [WARN] 
ShuffleTaskManager.preAllocatedBufferCheck - Remove expired 
preAllocatedBuffer[id=1213266] that required by app: 
application_1703049085550_4925739_1708775782306
   [2024-02-24 21:01:20.540] [expiredAppCleaner-0] [INFO] 
ShuffleTaskManager.checkResourceStatus - Detect expired 
appId[application_1703049085550_4925739_1708775782306] according to 
rss.server.app.expired.withoutHeartbeat
   [2024-02-24 21:01:20.547] [clearResourceThread] [INFO] 
ShuffleTaskManager.removeResources - Start remove resource for 
appId[application_1703049085550_4925739_1708775782306]
   [2024-02-24 21:01:21.078] [LocalFileFlushEventThreadPool-0] [ERROR] 
DefaultFlushEventHandler.handleEventAndUpdateMetrics - Unexpected exceptions 
happened due to
   java.lang.NullPointerException
   at 
org.apache.uniffle.server.ShuffleTaskInfo.getMaxConcurrencyPerPartitionToWrite(ShuffleTaskInfo.java:109)
   at 
org.apache.uniffle.server.ShuffleFlushManager.getMaxConcurrencyPerPartitionWrite(ShuffleFlushManager.java:198)
   at 
org.apache.uniffle.server.ShuffleFlushManager.processFlushEvent(ShuffleFlushManager.java:149)
   at 
org.apache.uniffle.server.DefaultFlushEventHandler.handleEventAndUpdateMetrics(DefaultFlushEventHandler.java:87)
   at 
org.apache.uniffle.server.DefaultFlushEventHandler.lambda$dispatchEvent$0(DefaultFlushEventHandler.java:203)
   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)
   
   As you can see, the exception will happen right after the appId is expired 
and the resources related to the appId are removed.
   
   I wanna discuss about it. What's the best way to avoid the exception?
   
   ### Affects Version(s)
   
   master
   
   ### Uniffle Server Log Output
   
   _No response_
   
   ### Uniffle Engine Log Output
   
   _No response_
   
   ### Uniffle Server Configurations
   
   _No response_
   
   ### Uniffle Engine Configurations
   
   _No response_
   
   ### Additional context
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to