[
https://issues.apache.org/jira/browse/YARN-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14630151#comment-14630151
]
Hadoop QA commented on YARN-433:
--------------------------------
\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | patch | 0m 0s | The patch command could not apply
the patch during dryrun. |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL |
http://issues.apache.org/jira/secure/attachment/12740222/YARN-433.2.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / 1ba2986 |
| Console output |
https://builds.apache.org/job/PreCommit-YARN-Build/8559/console |
This message was automatically generated.
> When RM is catching up with node updates then it should not expire acquired
> containers
> --------------------------------------------------------------------------------------
>
> Key: YARN-433
> URL: https://issues.apache.org/jira/browse/YARN-433
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Reporter: Bikas Saha
> Assignee: Xuan Gong
> Attachments: YARN-433.1.patch, YARN-433.2.patch
>
>
> RM expires containers that are not launched within some time of being
> allocated. The default is 10mins. When an RM is not keeping up with node
> updates then it may not be aware of new launched containers. If the expire
> thread fires for such containers then the RM can expire them even though they
> may have launched.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
