[jira] [Commented] (AMBARI-2856) NameNode HA Wizard: E2E integration for progress page after Create Checkpoint page

["Antonenko Alexander (JIRA)" <ji...@apache.org>]

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

Antonenko Alexander commented on AMBARI-2856:
---------------------------------------------

+1 for the patch
                
> NameNode HA Wizard: E2E integration for progress page after Create Checkpoint page
> ----------------------------------------------------------------------------------
>
>                 Key: AMBARI-2856
>                 URL: https://issues.apache.org/jira/browse/AMBARI-2856
>             Project: Ambari
>          Issue Type: Task
>          Components: client
>    Affects Versions: 1.4.0
>            Reporter: Aleksandr Kovalenko
>            Assignee: Aleksandr Kovalenko
>             Fix For: 1.4.0
>
>         Attachments: AMBARI-2856.patch
>
>
> Step 5 (Progress page after Create Checkpoint page)
> * "Stop All Services"
> make an API call to stop all services
> * "Install Additional NameNode"
> make an API call to install the additional NAMENODE component on the assigned host
> * "Install JournalNodes"
> make an API call to install the JOURNALNODE component on the assigned 3 hosts
> * "Start JournalNodes"
> make an API call to start all the JOURNALNODEs
> * "Disable Secondary NameNode"
> make an API call to change the state of the SECONDARY_NAMENODE to "MAINTENANCE" state
> * "Reconfigure HDFS"
> make an API call to install HDFS_CLIENT on the host(s) for the two NAMENODEs.  This pushes the config files (core-site and hdfs-site) to these hosts.  The backend takes care of pushing the config files even if these components are already installed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira