[ https://issues.apache.org/jira/browse/GEARPUMP-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16200186#comment-16200186 ]
ASF GitHub Bot commented on GEARPUMP-355: ----------------------------------------- Github user codecov-io commented on the issue: https://github.com/apache/incubator-gearpump/pull/231 # [Codecov](https://codecov.io/gh/apache/incubator-gearpump/pull/231?src=pr&el=h1) Report > Merging [#231](https://codecov.io/gh/apache/incubator-gearpump/pull/231?src=pr&el=desc) into [master](https://codecov.io/gh/apache/incubator-gearpump/commit/175b08e64c3363a2da9c61e05dac5f01d1f8db2d?src=pr&el=desc) will **increase** coverage by `0.01%`. > The diff coverage is `n/a`. ```diff @@ Coverage Diff @@ ## master #231 +/- ## ========================================== + Coverage 69.01% 69.03% +0.01% ========================================== Files 191 191 Lines 6119 6119 Branches 358 358 ========================================== + Hits 4223 4224 +1 + Misses 1896 1895 -1 ``` > AppMasterResolver fails to run against a kerberized Hadoop cluster > ------------------------------------------------------------------ > > Key: GEARPUMP-355 > URL: https://issues.apache.org/jira/browse/GEARPUMP-355 > Project: Apache Gearpump > Issue Type: Bug > Components: security, yarn > Affects Versions: 0.8.4 > Reporter: Timea Magyar > Fix For: 0.8.4 > > > When trying to launch a Gearpump cluster in a kerberized Hadoop/Yarn > environment, after the Application Master address has been resolved as a > prerequisite, the YarnAppMaster (responsible for starting GearPump masters, > workers, UI servers as Yarn containers) address (actor reference) must be > obtained via Kerberos/Spnego. (Kerberos over http) > The current implementation for this resides in the AppMasterResolver class > and is using an apache http client (version 3.x) for establishing a > connection to the Application Master and obtain the above YarnAppMaster actor > reference. Since the apache http client does not support the negotiate > authentication scheme in version 3.x (required for a connection over > kerberos/spnego) this step will always fail in a kerberized Yarn/Hadoop > cluster set-up. > I tested this in a secured/kerberized CDH 5.7.5 environment. I would like to > provide a patch for this by adapting the SPNEGO-enabled Hadoop web > connection code from WebHDFS. -- This message was sent by Atlassian JIRA (v6.4.14#64029)