You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "bhuvnesh chaudhary (JIRA)" <ji...@apache.org> on 2016/04/28 23:49:13 UTC
[jira] [Updated] (AMBARI-16172) HAWQ Configuration should be
updated whenever Namenode is being moved.
[ https://issues.apache.org/jira/browse/AMBARI-16172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
bhuvnesh chaudhary updated AMBARI-16172:
----------------------------------------
Fix Version/s: 2.2.0
Status: Patch Available (was: Open)
> 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
>
>
> 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)