Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ambari-dev@incubator.apache.org
Date: Mon, 8 Apr 2013 16:55:17 +0000 (UTC)
From: "Sumit Mohanty (JIRA)" <jira@apache.org>
To: ambari-dev@incubator.apache.org
Message-ID: <JIRA.12640828.1365099583423.128318.1365440117770@arcas>
In-Reply-To: <JIRA.12640828.1365099583423@arcas>
References: <JIRA.12640828.1365099583423@arcas>
Subject: [jira] [Resolved] (AMBARI-1789) Stopping and then Starting all
 services doesn't start NameNode
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Sumit Mohanty resolved AMBARI-1789.
-----------------------------------

    Resolution: Fixed
    
> Stopping and then Starting all services doesn't start NameNode
> --------------------------------------------------------------
>
>                 Key: AMBARI-1789
>                 URL: https://issues.apache.org/jira/browse/AMBARI-1789
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 1.3.0
>            Reporter: Sumit Mohanty
>            Assignee: Sumit Mohanty
>             Fix For: 1.3.0
>
>         Attachments: AMBARI-1789.patch
>
>
> Security wizard stops all services, applies configuration and then starts all services.
> Sometimes it has been noticed that the action to stop all service completes successfully but the action to start all services never sends the task to start NameNode.

--
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