[
https://issues.apache.org/jira/browse/YARN-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14551092#comment-14551092
]
Hadoop QA commented on YARN-3560:
---------------------------------
\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | patch | 0m 0s | The patch command could not apply
the patch during dryrun. |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL |
http://issues.apache.org/jira/secure/attachment/12733403/YARN-3560.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / e422e76 |
| Console output |
https://builds.apache.org/job/PreCommit-YARN-Build/8007/console |
This message was automatically generated.
> Not able to navigate to the cluster from tracking url (proxy) generated after
> submission of job
> -----------------------------------------------------------------------------------------------
>
> Key: YARN-3560
> URL: https://issues.apache.org/jira/browse/YARN-3560
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.7.0
> Reporter: Anushri
> Priority: Minor
> Attachments: YARN-3560.patch
>
>
> a standalone web proxy server is enabled in the cluster
> when a job is submitted the url generated contains proxy
> track this url
> in the web page , if we try to navigate to the cluster links [about.
> applications, or scheduler] it gets redirected to some default port instead
> of actual RM web port configured
> as such it throws "webpage not available"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)