You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2016/05/17 14:58:13 UTC
[jira] [Updated] (MAPREDUCE-6701) application master log can not be
available when clicking jobhistory's am logs link
[ https://issues.apache.org/jira/browse/MAPREDUCE-6701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Lowe updated MAPREDUCE-6701:
----------------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 2.9.0
Status: Resolved (was: Patch Available)
Thanks to [~haibochen] for the contribution and to [~rkanter] for additional review! I committed this to trunk and branch-2.
> application master log can not be available when clicking jobhistory's am logs link
> -----------------------------------------------------------------------------------
>
> Key: MAPREDUCE-6701
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6701
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobhistoryserver
> Affects Versions: 2.9.0
> Reporter: chenyukang
> Assignee: Haibo Chen
> Priority: Critical
> Fix For: 2.9.0
>
> Attachments: yarn5041.001.patch, yarn5041.002.patch
>
>
> In history server webapp, application master logs link is wrong. it shows "No logs available for container container_1462419429440_0003_01_000001". It direct to a wrong nodemanager http port instead of a node manager' container managerment port. I think YARN-4701 brought this bug
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-help@hadoop.apache.org