Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 0CC96200D20 for ; Tue, 17 Oct 2017 17:43:21 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 0AF351609DE; Tue, 17 Oct 2017 15:43:21 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 47C741609D7 for ; Tue, 17 Oct 2017 17:43:20 +0200 (CEST) Received: (qmail 13910 invoked by uid 500); 17 Oct 2017 15:43:19 -0000 Mailing-List: contact dev-help@gearpump.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@gearpump.incubator.apache.org Delivered-To: mailing list dev@gearpump.incubator.apache.org Delivered-To: moderator for dev@gearpump.incubator.apache.org Received: (qmail 4230 invoked by uid 99); 17 Oct 2017 06:26:41 -0000 X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -4.021 X-Spam-Level: X-Spam-Status: No, score=-4.021 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001] autolearn=disabled From: titikakatoo To: dev@gearpump.incubator.apache.org Reply-To: dev@gearpump.incubator.apache.org References: In-Reply-To: Subject: [GitHub] incubator-gearpump issue #231: [GEARPUMP-355] Fix YarnAppMaster address reso... Content-Type: text/plain Message-Id: <20171017062638.43421DFB32@git1-us-west.apache.org> Date: Tue, 17 Oct 2017 06:26:38 +0000 (UTC) archived-at: Tue, 17 Oct 2017 15:43:21 -0000 Github user titikakatoo commented on the issue: https://github.com/apache/incubator-gearpump/pull/231 Hi @huafengw, I haven't set the cluster up myself. It is one of our corporate CDH 5.11.1 Hadoop cluster shared across multiple departments, secured by Kerberos/Reverse Proxy/SSL. It is a 10 node cluster located in the company's data center and protected by a corporate firewall (Security Layer 4) and accessible only via application/edge servers with sufficient firewall rules to access cluster services. The above cluster was set up by our corporate CI department in cooperation with Cloudera and it is mostly leaned on standard Cloudera 5 security guidelines, nothing special in this respect. The **YarnClient/Gear** commands are all executed from one of our edge nodes, by an appropriate Kerberos principal. ---