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

Posted to dev@ambari.apache.org by "Yusaku Sako (JIRA)" <ji...@apache.org> on 2014/01/16 01:45:20 UTC

[jira] [Commented] (AMBARI-4244) NameNode start fails after moving it to another host

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

Yusaku Sako commented on AMBARI-4244:
-------------------------------------

+1 by Review Board.

Committed to trunk and branch-1.4.4.

> NameNode start fails after moving it to another host
> ----------------------------------------------------
>
>                 Key: AMBARI-4244
>                 URL: https://issues.apache.org/jira/browse/AMBARI-4244
>             Project: Ambari
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.4.3
>            Reporter: Yusaku Sako
>            Assignee: Yusaku Sako
>             Fix For: 1.5.0, 1.4.4
>
>         Attachments: AMBARI-4244.patch
>
>
> After moving the NameNode via Reassign Wizard, NameNode fails to come up.  This is because of the way the wizard updates *hbase.rootdir*.  It drops the port.  Technically this is fine, but Ambari agent does not like this and causes NameNode start failure.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)