Return-Path: <issues-return-8257-archive-asf-public=cust-asf.ponee.io@ambari.apache.org>
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 670822009D9
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Mon,  2 May 2016 20:47:14 +0200 (CEST)
Received: by cust-asf.ponee.io (Postfix)
	id 65D251609B1; Mon,  2 May 2016 20:47:14 +0200 (CEST)
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 B56E51609B0
	for <archive-asf-public@cust-asf.ponee.io>; Mon,  2 May 2016 20:47:13 +0200 (CEST)
Received: (qmail 59292 invoked by uid 500); 2 May 2016 18:47:13 -0000
Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@ambari.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@ambari.apache.org>
List-Post: <mailto:issues@ambari.apache.org>
List-Id: <issues.ambari.apache.org>
Reply-To: dev@ambari.apache.org
Delivered-To: mailing list issues@ambari.apache.org
Received: (qmail 59274 invoked by uid 99); 2 May 2016 18:47:12 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 May 2016 18:47:12 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id D051F2C1F5C
	for <issues@ambari.apache.org>; Mon,  2 May 2016 18:47:12 +0000 (UTC)
Date: Mon, 2 May 2016 18:47:12 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.12963968.1461962878000.88655.1462214832850@Atlassian.JIRA>
In-Reply-To: <JIRA.12963968.1461962878000@Atlassian.JIRA>
References: <JIRA.12963968.1461962878000@Atlassian.JIRA> <JIRA.12963968.1461962878611@arcas>
Subject: [jira] [Commented] (AMBARI-16191) HAWQ Configuration should be
 updated whenever Namenode is being moved
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
archived-at: Mon, 02 May 2016 18:47:14 -0000


    [ https://issues.apache.org/jira/browse/AMBARI-16191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15267241#comment-15267241 ] 

Hudson commented on AMBARI-16191:
---------------------------------

SUCCESS: Integrated in Ambari-branch-2.2 #682 (See [https://builds.apache.org/job/Ambari-branch-2.2/682/])
AMBARI-16191: HAWQ Configuration should be updated whenever Namenode is (bchaudhary: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=97b754139847f8ee0ac6f71fb3f4ffb7f98d34c9])
* ambari-web/app/controllers/main/service/reassign/step4_controller.js
* ambari-web/test/controllers/main/service/reassign/step4_controller_test.js


> HAWQ Configuration should be updated whenever Namenode is being moved
> ---------------------------------------------------------------------
>
>                 Key: AMBARI-16191
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16191
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.4.0
>            Reporter: bhuvnesh chaudhary
>            Assignee: bhuvnesh chaudhary
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-16191.patch
>
>
> HAWQ Configuration should be updated whenever Namenode is being moved using the move namenode wizard.
> Parameters which should be updated
> Case 1: HDFS HA
> hdfs-client parameters under HAWQ service
> dfs.namenode.rpc-address.<nameservice>.<nnid>
> dfs.namenode.http-address.<nameservice>.<nnid>
> Case 2: Non HA HDFS
> hawq-site parmeters under HAWQ service
> hawq_dfs_url



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)