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

Andrew Onischuk updated AMBARI-23490:
-------------------------------------
    Status: Patch Available  (was: Open)

> NN Federation Wizard: Bootstrap NameNode failed
> -----------------------------------------------
>
>                 Key: AMBARI-23490
>                 URL: https://issues.apache.org/jira/browse/AMBARI-23490
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>            Priority: Major
>             Fix For: 2.7.0
>
>         Attachments: AMBARI-23490.patch
>
>
> Bootstrap NameNode command fails due to stopped NameNode. Actually NameNode
> should be started and command to start it was sent correctly from UI, but was
> ignored by BE due to:
>     
>     
>     Ignoring ServiceComponentHost as the current state matches the new 
> desired state, clusterName=c, serviceName=HDFS, componentName=NAMENODE, 
> hostname=c7404.ambari.apache.org, currentState=STARTED, 
> newDesiredState=STARTED
> This is because Format NameNode command starts NameNode for a little period of
> time and then stops it back, but component's current state is not updated
> immediately and BE thinks that NameNode is still started.  
> From Format NameNode log:
>     
>     
>     
>     18/04/04 11:44:31 INFO namenode.NameNode: STARTUP_MSG: 
>     /************************************************************
>     STARTUP_MSG: Starting NameNode
>     
>     ...
>     
>     18/04/04 11:44:35 INFO namenode.NameNode: SHUTDOWN_MSG: 
>     /************************************************************
>     SHUTDOWN_MSG: Shutting down NameNode at 
> c7404.ambari.apache.org/192.168.74.104
>     



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to