You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/04/06 09:21:00 UTC

[jira] [Commented] (AMBARI-23490) NN Federation Wizard: Bootstrap NameNode failed

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

Hudson commented on AMBARI-23490:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8999 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8999/])
AMBARI-23490. NN Federation Wizard: Bootstrap NameNode failed (aonishuk) (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=23f47a3bad70e0799a826ca2f11480b3c0544cbe])
* (edit) ambari-agent/src/main/python/ambari_agent/ComponentStatusExecutor.py
* (edit) ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py


> 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
>              Labels: pull-request-available
>             Fix For: 2.7.0
>
>         Attachments: AMBARI-23490.patch, AMBARI-23490.patch
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> 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)