ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yusaku Sako (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-4244) NameNode start fails after moving it to another host
Date Wed, 08 Jan 2014 22:34:50 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Yusaku Sako updated AMBARI-4244:
--------------------------------

    Attachment: AMBARI-4244.patch

> 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.4.3
>
>         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)

Mime
View raw message