[
https://issues.apache.org/jira/browse/GEARPUMP-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16200140#comment-16200140
]
ASF GitHub Bot commented on GEARPUMP-354:
-----------------------------------------
Github user codecov-io commented on the issue:
https://github.com/apache/incubator-gearpump/pull/230
#
[Codecov](https://codecov.io/gh/apache/incubator-gearpump/pull/230?src=pr&el=h1)
Report
> Merging
[#230](https://codecov.io/gh/apache/incubator-gearpump/pull/230?src=pr&el=desc)
into
[master](https://codecov.io/gh/apache/incubator-gearpump/commit/175b08e64c3363a2da9c61e05dac5f01d1f8db2d?src=pr&el=desc)
will **increase** coverage by `1.17%`.
> The diff coverage is `n/a`.
```diff
@@ Coverage Diff @@
## master #230 +/- ##
==========================================
+ Coverage 69.01% 70.19% +1.17%
==========================================
Files 191 191
Lines 6119 6119
Branches 358 358
==========================================
+ Hits 4223 4295 +72
+ Misses 1896 1824 -72
```
> 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)
