hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (YARN-5080) Cannot obtain logs using YARN CLI -am for either KILLED or RUNNING AM
Date Sun, 15 May 2016 20:01:12 GMT

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

Vinod Kumar Vavilapalli reopened YARN-5080:

[~xgong] / [~djp], the patch was +1ed and committed even though it wasn't run through Jenkins!

Doesn't look like this broke compilation, but let's please not do this.

W.r.t the patch itself, using {{WebAppUtils.getRMWebAppURLWithScheme()}} will not address
the case where RM uses a different bind-host configuration - I'm not entirely sure if this
is the right fix.

Reopening JIRA for running it through Jenkins and for more discussion.

> Cannot obtain logs using YARN CLI -am for either KILLED or RUNNING AM
> ---------------------------------------------------------------------
>                 Key: YARN-5080
>                 URL: https://issues.apache.org/jira/browse/YARN-5080
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: yarn
>    Affects Versions: 2.8.0
>            Reporter: Sumana Sathish
>            Assignee: Xuan Gong
>            Priority: Critical
>             Fix For: 2.8.0
>         Attachments: YARN-5080.1.patch
> When the application is running, if we try to obtain AM logs using 
> {code}
> yarn logs -applicationId <applicationId> -am 1
> {code}
> It throws the following error
> {code}
> Unable to get AM container informations for the application:<applicationId>
> Illegal character in scheme name at index 0:<hostname>
> {code} 

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message