[ https://issues.apache.org/jira/browse/YARN-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14288218#comment-14288218 ]
Jason Lowe commented on YARN-3090: ---------------------------------- An easy way to at least log a message when something terrible occurrs to a deletion task is to use a derived ScheduledThreadPoolExecutor that overrides the afterExecute method to log any throwable that was associated with the task. > DeletionService can silently ignore deletion task failures > ---------------------------------------------------------- > > Key: YARN-3090 > URL: https://issues.apache.org/jira/browse/YARN-3090 > Project: Hadoop YARN > Issue Type: Bug > Components: nodemanager > Affects Versions: 2.1.1-beta > Reporter: Jason Lowe > > If a non-I/O exception occurs while the DeletionService is executing a > deletion task then it will be silently ignored. The exception bubbles up to > the thread workers of the ScheduledThreadPoolExecutor which simply attaches > the throwable to the Future that was returned when the task was scheduled. > However the thread pool is used as a fire-and-forget pool, so nothing ever > looks at the Future and therefore the exception is never logged. -- This message was sent by Atlassian JIRA (v6.3.4#6332)