[
https://issues.apache.org/jira/browse/YARN-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15284664#comment-15284664
]
Junping Du commented on YARN-5080:
----------------------------------
[~vinodkv], the Jenkins test was actually kicked off but failed to post here:
https://builds.apache.org/job/PreCommit-YARN-Build/11442/ (test failures are
not related and get tracked in YARN-4982). The same thing keep happening during
the same time for other JIRAs like YARN-4325, etc., so I didn't mention it
before in my previous review.
About the patch, I think you are right that we missed the case for different RM
bind-host configuration "yarn.resourcemanager.bind-host". However, the existing
{{WebAppUtils.getWebAppBindURL()}} seems doesn't handle well when bind-host is
set to "0.0.0.0".
May be the right fix could be add an explicitly check in
WebAppUtils.getWebAppBindURL() to skip host injection if hostProperty is set to
"0.0.0.0". [~xgong] and [~vinodkv], what do you think?
> 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: 0.0.0.0://<hostname>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
