Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 22 Nov 2016 08:51:58 +0000 (UTC)
From: "Weiwei Yang (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.13020970.1479252398000.336669.1479804718537@Atlassian.JIRA>
In-Reply-To: <JIRA.13020970.1479252398000@Atlassian.JIRA>
References: <JIRA.13020970.1479252398000@Atlassian.JIRA> <JIRA.13020970.1479252398168@arcas>
Subject: [jira] [Commented] (HDFS-11143) start.sh doesn't return any error
 message even namenode is not up.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 22 Nov 2016 08:52:00 -0000


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

Weiwei Yang commented on HDFS-11143:
------------------------------------

I don't think Hadoop scripts really handle that much, it mostly was handled by higher level management providers, such as ambari. So this is not a bug. This is good to have, as a more general task than just namenode.

> start.sh doesn't return any error message even namenode is not up.
> ------------------------------------------------------------------
>
>                 Key: HDFS-11143
>                 URL: https://issues.apache.org/jira/browse/HDFS-11143
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Yufei Gu
>


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org