[
https://issues.apache.org/jira/browse/GEARPUMP-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16200122#comment-16200122
]
ASF GitHub Bot commented on GEARPUMP-354:
-----------------------------------------
GitHub user titikakatoo opened a pull request:
https://github.com/apache/incubator-gearpump/pull/230
[GEARPUMP-354] Fix the tracking url resolution of a proxied Applicati…
…on Master
Be sure to do all of the following to help us incorporate your contribution
quickly and easily:
- [ ] Make sure the commit message is formatted like:
`[GEARPUMP-<Jira issue #>] Meaningful description of pull request`
- [ ] Make sure tests pass via `sbt clean test`.
- [ ] Make sure old documentation affected by the pull request has been
updated and new documentation added for new functionality.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/titikakatoo/incubator-gearpump
resolve_app_master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-gearpump/pull/230.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #230
----
commit 224d77a2ae1d82a7947c0c0e6447c94440a43117
Author: Timea Magyar <[email protected]>
Date: 2017-10-11T11:14:56Z
[GEARPUMP-354] Fix the tracking url resolution of a proxied Application
Master
----
> 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)
