[jira] [Updated] (YARN-4037) Hadoop - failed redirect for container

["Gagan (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/YARN-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gagan updated YARN-4037:
------------------------
    Attachment: mapred-site.xml
                yarn-site.xml

Hi Mohammad,

May be I am making a fundamental mistake.

My target is to run - wordcount example jar with 2.7.1 on yarn in a psuedo distributed mode (on my laptop). 

When I run it I get an exception, in order to check what it is  I am trying to look for logs at 
http://garima-pc:8088/cluster/apps/FAILED to http://garima-pc:8088/cluster/app/application_1439303739376_0001 to logs link and after implementing what you have described it takes me to a link
http://garima-pc:19888/jobhistory/logs/Garima-PC:50415/container_1439303739376_0001_02_000001/container_1439303739376_0001_02_000001/Garima
which is broken. seems like port 50415 port is getting dynamically generated.
I am attaching my configuration xml files.

> Hadoop - failed redirect for container
> --------------------------------------
>
>                 Key: YARN-4037
>                 URL: https://issues.apache.org/jira/browse/YARN-4037
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: yarn
>    Affects Versions: 2.7.1
>         Environment: Windows 7, Apache Hadoop 2.7.1
>            Reporter: Gagan
>         Attachments: mapred-site.xml, yarn-site.xml
>
>
> I believe this issue has been addressed earlier in https://issues.apache.org/jira/browse/YARN-1473 though I am not sure because the description of the JIRA does not talk about the following message 
> Failed while trying to construct the redirect url to the log server. Log Server url may not be configured
> java.lang.Exception: Unknown container. Container either has not started or has already completed or doesn't belong to this node at all.
> Could some one look at the same and provide detail on the root cause and resolution ?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)