[
https://issues.apache.org/jira/browse/YARN-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14313211#comment-14313211
]
Hadoop QA commented on YARN-3090:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12697529/YARN-3090.004.patch
against trunk revision aab459c.
{color:red}-1 @author{color}. The patch appears to contain @author tags
which the Hadoop community has agreed to not allow in code contributions.
{color:green}+1 tests included{color}. The patch appears to include new
or modified test files.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6561//console
This message is automatically generated.
> 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
> Assignee: Varun Saxena
> Attachments: YARN-3090.001.patch, YARN-3090.002.patch,
> YARN-3090.003.patch, YARN-3090.004.patch
>
>
> 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)
