[
https://issues.apache.org/jira/browse/AMBARI-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13796915#comment-13796915
]
Aleksandr Kovalenko commented on AMBARI-3526:
---------------------------------------------
committed to trunk
> Reassign Master: HDFS service check fails after Namenode reassignment with HA
> enabled
> -------------------------------------------------------------------------------------
>
> Key: AMBARI-3526
> URL: https://issues.apache.org/jira/browse/AMBARI-3526
> Project: Ambari
> Issue Type: Task
> Components: client
> Affects Versions: 1.4.2
> Reporter: Aleksandr Kovalenko
> Assignee: Aleksandr Kovalenko
> Priority: Critical
> Fix For: 1.4.2
>
> Attachments: AMBARI-3526.patch, reassign-step-4.png
>
>
> We need to make three changes to the wizard.
> # Step-4 (reassign-step4.png) needs to have first command as Stop NameNode.
> This command should stop namenode component on the selected source host. This
> is to makes sure that the selected namenode host to be moved becomes standby
> before we proceed ahead.
> # We need to add one more step to the wizard after step-4 (Install, Start and
> Test). The mockup and purpose of this new step is exactly same as of step7
> (Start Components) in namenode HA wizard. Start NameNode command in this step
> should start active namenode. Active namenode should be on a host which was
> *not selected* as source host to be moved in the wizard.
> # There is only one manual command required on manual command page. The
> message for it should be like:
> * Login to the newly installed NameNode host <target host hostname>
> * Initialize the metadata by running:
> {quote}
> sudo su -l hdfs -c 'hdfs namenode -bootstrapStandby'
> {quote}
> * Proceed next
--
This message was sent by Atlassian JIRA
(v6.1#6144)
