[jira] [Commented] (AMBARI-16172) HAWQ Configuration should be updated whenever Namenode is being moved.

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-16172:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12801328/AMBARI-16172-branch-2.2.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/6718//console

This message is automatically generated.

> HAWQ Configuration should be updated whenever Namenode is being moved.
> ----------------------------------------------------------------------
>
>                 Key: AMBARI-16172
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16172
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.2.0
>            Reporter: bhuvnesh chaudhary
>            Assignee: bhuvnesh chaudhary
>             Fix For: 2.2.0
>
>         Attachments: AMBARI-16172-branch-2.2.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)