Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <7367763.1259101359675.JavaMail.jira@brutus>
Date: Tue, 24 Nov 2009 22:22:39 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Resolved: (HBASE-1958) Remove "# TODO: PUT BACK !!!
 "${HADOOP_HOME}"/bin/hadoop dfsadmin -safemode wait"
In-Reply-To: <864417875.1257547112506.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack resolved HBASE-1958.
--------------------------

    Resolution: Fixed

Removed the line.  We wait on hdfs to leave safe mode up in java code, not in shell.

> Remove "# TODO: PUT BACK !!! "${HADOOP_HOME}"/bin/hadoop dfsadmin -safemode wait"
> ---------------------------------------------------------------------------------
>
>                 Key: HBASE-1958
>                 URL: https://issues.apache.org/jira/browse/HBASE-1958
>             Project: Hadoop HBase
>          Issue Type: Task
>            Reporter: stack
>
> In start-hbase.sh there is the above comment.  Was done as part of the below:
> {code}
> ------------------------------------------------------------------------
> r618560 | stack | 2008-02-04 22:15:44 -0800 (Mon, 04 Feb 2008) | 14 lines
> HBASE-403 Fix build after move of hbase in svn
> Make it so scripts basically work again.  Make up a log4j
> basic properites file (currently broke).
> M    trunk/conf/hbase-env.sh
>     Put a JAVA_HOME in here.  Need to set it here now instead of up in hadoop-env
> A    trunk/conf/log4j.properties
>     Basic log4j for hbase.
> M    trunk/bin/hbase
>     Made pointers up into hadoop instead point to hbase substitutions.
> M    trunk/bin/start-hbase.sh
>     Remove wait on dfs for moment.  Need to figure how to do it now
>     we're detached (Besides there is talk that we'd acually 
> {code}
> The comment doesn't seem to apply any more because we wait up in java.  This issue is about cleaning up this remark.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.