You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Aleksandr Kovalenko (JIRA)" <ji...@apache.org> on 2013/11/05 15:41:18 UTC

[jira] [Commented] (AMBARI-3683) NameNode HA: Reconfigure dfs.namenode.https-address property in hdfs-site.xml

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

Aleksandr Kovalenko commented on AMBARI-3683:
---------------------------------------------

+1 for the patch

> NameNode HA: Reconfigure dfs.namenode.https-address property in hdfs-site.xml
> -----------------------------------------------------------------------------
>
>                 Key: AMBARI-3683
>                 URL: https://issues.apache.org/jira/browse/AMBARI-3683
>             Project: Ambari
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.4.2
>            Reporter: Antonenko Alexander
>            Assignee: Antonenko Alexander
>             Fix For: 1.4.2
>
>         Attachments: AMBARI-3683.patch
>
>
> We reconfigure dfs.namenode.http-address property with logical name in hdfs-site.xml while enabling NameNode HA. 
> dfs.namenode.https-address is persisted with one namenode hostname as of now.



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