From hdfs-issues-return-249925-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Fri Feb 1 06:45:05 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 24B38180627 for ; Fri, 1 Feb 2019 07:45:04 +0100 (CET) Received: (qmail 64911 invoked by uid 500); 1 Feb 2019 06:45:04 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 64885 invoked by uid 99); 1 Feb 2019 06:45:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Feb 2019 06:45:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 6EC59180779 for ; Fri, 1 Feb 2019 06:45:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id ddlSM3VRCktN for ; Fri, 1 Feb 2019 06:45:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 8A80F5F5AB for ; Fri, 1 Feb 2019 06:45:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 0B20AE26B0 for ; Fri, 1 Feb 2019 06:45:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 5CAE7243D5 for ; Fri, 1 Feb 2019 06:45:00 +0000 (UTC) Date: Fri, 1 Feb 2019 06:45:00 +0000 (UTC) From: =?utf-8?Q?=C3=8D=C3=B1igo_Goiri_=28JIRA=29?= To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HDFS-14118) Use DNS to resolve Namenodes and Routers MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-14118?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:all-tabpanel ] =C3=8D=C3=B1igo Goiri updated HDFS-14118: ------------------------------- Attachment: (was: HDFS-14118.012.patch) > Use DNS to resolve Namenodes and Routers > ---------------------------------------- > > Key: HDFS-14118 > URL: https://issues.apache.org/jira/browse/HDFS-14118 > Project: Hadoop HDFS > Issue Type: New Feature > Reporter: Fengnan Li > Assignee: Fengnan Li > Priority: Major > Attachments: DNS testing log, HDFS-14118.001.patch, HDFS-14118.00= 2.patch, HDFS-14118.003.patch, HDFS-14118.004.patch, HDFS-14118.005.patch, = HDFS-14118.006.patch, HDFS-14118.007.patch, HDFS-14118.008.patch, HDFS-1411= 8.009.patch, HDFS-14118.010.patch, HDFS-14118.011.patch, HDFS-14118.patch > > > Clients will need to know about routers to talk to the HDFS cluster (obvi= ously), and having routers updating (adding/removing) will have to make eve= ry client change, which is a painful process. > DNS can be used here to resolve the single domain name clients knows to a= list of routers in the current config. However, DNS won't be able to consi= der only resolving to the working router based on certain health thresholds= . > There are some ways about how this can be solved. One way is to have a se= parate script to regularly check the status of the router and update the DN= S records if a router fails the health thresholds. In this way, security mi= ght be carefully considered for this way. Another way is to have the client= do the normal connecting/failover after they get the list of routers, whic= h requires the change of current failover proxy provider. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org