[
https://issues.apache.org/jira/browse/YARN-4281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14965490#comment-14965490
]
Hadoop QA commented on YARN-4281:
---------------------------------
\\
\\
| (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/12767633/YARN-4281.2.7.modify.patch
|
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / 6381ddc |
| Console output |
https://builds.apache.org/job/PreCommit-YARN-Build/9493/console |
This message was automatically generated.
> 2.7 RM app page is broken
> -------------------------
>
> Key: YARN-4281
> URL: https://issues.apache.org/jira/browse/YARN-4281
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Chang Li
> Assignee: Chang Li
> Fix For: 2.7.2
>
> Attachments: YARN-4281.2.7.modify.patch
>
>
> 2.7 RM app page is broken by the cherry pick of YARN-3248 on 23/Sep. It broke
> the work around 2.7 patch of YARN-3544 to let it still use container report.
> Currently, our cluster's 2.7 RM app page is completely broken due to 500
> error, which is caused by when user UGI is null, completed app can not
> retrieve its container report, and in that code path, it doesn't catch
> ContainerNotFoundException, but throw the exception, therefore cause the 500
> error.
> Running app is also broken because of the way it construct containerID by
> {code} "ContainerId.newContainerId(
> appAttemptReport.getApplicationAttemptId(), 1)"
> {code},
> which will not include epoch number, so it will also get
> ContainerNotFoundException and throw 500 error.
> Propose to use the branch-2 version of YARN-3544, instead of the work around
> 2.7 patch because branch 2 patch on 2.7 is no longer blocked.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
