Return-Path: X-Original-To: apmail-ambari-user-archive@www.apache.org Delivered-To: apmail-ambari-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 327EF10928 for ; Wed, 28 May 2014 06:17:40 +0000 (UTC) Received: (qmail 16204 invoked by uid 500); 28 May 2014 06:17:40 -0000 Delivered-To: apmail-ambari-user-archive@ambari.apache.org Received: (qmail 16175 invoked by uid 500); 28 May 2014 06:17:40 -0000 Mailing-List: contact user-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ambari.apache.org Delivered-To: mailing list user@ambari.apache.org Received: (qmail 16167 invoked by uid 99); 28 May 2014 06:17:40 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 May 2014 06:17:39 +0000 X-ASF-Spam-Status: No, hits=-2.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_HI,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of line@vmware.com designates 208.91.2.12 as permitted sender) Received: from [208.91.2.12] (HELO smtp-outbound-1.vmware.com) (208.91.2.12) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 May 2014 06:17:34 +0000 Received: from sc9-mailhost3.vmware.com (sc9-mailhost3.vmware.com [10.113.161.73]) by smtp-outbound-1.vmware.com (Postfix) with ESMTP id 4F9A8994FF for ; Tue, 27 May 2014 23:17:14 -0700 (PDT) Received: from zcs-prod-mta-2.vmware.com (zcs-prod-mta-2.vmware.com [10.113.163.64]) by sc9-mailhost3.vmware.com (Postfix) with ESMTP id 4B47445806 for ; Tue, 27 May 2014 23:17:14 -0700 (PDT) Received: from zcs-prod-mta-2.vmware.com (localhost.localdomain [127.0.0.1]) by zcs-prod-mta-2.vmware.com (Postfix) with ESMTP id 3B653E004E; Tue, 27 May 2014 23:17:14 -0700 (PDT) Received: from zcs-prod-mbox-42.vmware.com (lbv-sc9-t2prod2-int.vmware.com [10.113.160.246]) by zcs-prod-mta-2.vmware.com (Postfix) with ESMTP; Tue, 27 May 2014 23:17:14 -0700 (PDT) Date: Tue, 27 May 2014 23:17:12 -0700 (PDT) From: Emma Lin To: user@ambari.apache.org Cc: Xiaoding Bian Cloud Services RANDD - 72410 , Qing Chi 79624 Message-ID: <792281067.34639587.1401257832992.JavaMail.root@vmware.com> In-Reply-To: <344059335.34632717.1401257084056.JavaMail.root@vmware.com> References: <344059335.34632717.1401257084056.JavaMail.root@vmware.com> Subject: Re: Question about how to change name node ip address after cluster is created by Ambari MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_34639586_1133650693.1401257832991" X-Originating-IP: [10.113.163.67] X-Mailer: Zimbra 8.0.3_GA_5664 (ZimbraWebClient - FF29 (Mac)/8.0.3_GA_5664) Thread-Topic: Question about how to change name node ip address after cluster is created by Ambari Thread-Index: 8rKGf6c3x0TBUQv6Yct/vUudmdmzaRul9ikm X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_34639586_1133650693.1401257832991 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hello guys, I'm working on provisioning cluster through Ambari now. But we're use DHCP network, and the ip address might be changed after the cluster is created. Either while the node is restarted, or the IP address of one node might be changed directly by DHCP server. So I want to know if there is easy solution from Ambari to handle such issue. The ip change might happen for all of nodes, including name node, jobtracker/resource manager, etc. I didn't get any information for this topic from the Ambari document. Your any comment is appreciated. thanks, Emma ------=_Part_34639586_1133650693.1401257832991 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

He= llo guys,
I'm working on provisioning cluster through Ambari = now. But we're use DHCP network, and the ip address might be changed after = the cluster is created. Either while the node is restarted, or the IP addre= ss of one node might be changed directly by DHCP server.

So I want to know if there is easy solution from Ambari to handle = such issue. The ip change might happen for all of nodes, including name nod= e, jobtracker/resource manager, etc.

I didn't= get any information for this topic from the Ambari document. Your any comm= ent is appreciated.

thanks,
Emma=

------=_Part_34639586_1133650693.1401257832991--