[
https://issues.apache.org/jira/browse/GEARPUMP-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16200172#comment-16200172
]
ASF GitHub Bot commented on GEARPUMP-354:
-----------------------------------------
Github user manuzhang commented on the issue:
https://github.com/apache/incubator-gearpump/pull/230
R: @karol-brejna-i @huafengw
> The tracking URL of a proxied Application Master can't be resolved when
> launching Gearpump on Yarn
> --------------------------------------------------------------------------------------------------
>
> Key: GEARPUMP-354
> URL: https://issues.apache.org/jira/browse/GEARPUMP-354
> Project: Apache Gearpump
> Issue Type: Bug
> Components: yarn
> Affects Versions: 0.8.4
> Reporter: Timea Magyar
> Priority: Critical
> Fix For: 0.8.4
>
>
> When I was testing the launch of a GEARPUMP cluster on secured Yarn, the
> proxied application master path could not be resolved properly. Looking at
> the GEARPUMP source code it turned out that instead of invoking the tracking
> url on the application report the original tracking url was used instead.
> This will never work in a proxied AM set up. In contrary invoking the
> tracking url will always work in a proxied and non-proxied environment alike.
> I created a small patch for this.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
