[jira] [Commented] (AMBARI-3735) Reassign Master: moving the NameNode while NameNode HA is enabled breaks HBase

["Aleksandr Kovalenko (JIRA)" <ji...@apache.org>]

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

Aleksandr Kovalenko commented on AMBARI-3735:
---------------------------------------------

+1 for the patch

> Reassign Master: moving the NameNode while NameNode HA is enabled breaks HBase
> ------------------------------------------------------------------------------
>
>                 Key: AMBARI-3735
>                 URL: https://issues.apache.org/jira/browse/AMBARI-3735
>             Project: Ambari
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.4.2
>            Reporter: Oleg Nechiporenko
>            Assignee: Oleg Nechiporenko
>             Fix For: 1.4.2
>
>         Attachments: AMBARI-3735.patch
>
>
> With NameNode HA enabled, move one of the NameNodes to another host.
> During the final "Start all services" task of the Reassign Master wizard, HBase service check fails.
> This is because the Reassign Master wizard incorrectly sets *hbase.rootdir* in *hbase-site.xml* to *hdfs://<new-namenode-host>/apps/hbase/data*.
> When HA is enabled, the value of *hbase.rootdir* should always be *hdfs://<nameservice-id>/apps/hbase/data*.
> Also, Reassign Master does not handle *dfs.namenode.https-address.<nameservice-id>.nn[1|2]* parameters in *hdfs-site.xml* properly; it does not update the value to use the new NameNode host.  On the other hand *dfs.namenode.http-address.<nameservice-id>.nn[1|2] parameters are handled properly already.



--
This message was sent by Atlassian JIRA
(v6.1#6144)