hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-6701) application master log can not be available when clicking jobhistory's am logs link
Date Tue, 17 May 2016 15:41:13 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-6701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15286869#comment-15286869
] 

Hudson commented on MAPREDUCE-6701:
-----------------------------------

ABORTED: Integrated in Hadoop-trunk-Commit #9793 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/9793/])
MAPREDUCE-6701. application master log can not be available when (jlowe: rev 12fa4ec141f8d0cb105b6f60c3739a4b26890fd5)
* hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs/src/main/java/org/apache/hadoop/mapreduce/v2/hs/webapp/HsJobBlock.java
* hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs/src/test/java/org/apache/hadoop/mapreduce/v2/hs/webapp/TestHsWebServicesJobs.java
* hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs/src/main/java/org/apache/hadoop/mapreduce/v2/hs/webapp/dao/AMAttemptInfo.java


> 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


Mime
View raw message