Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of saint.ack@gmail.com
 designates 209.85.215.169 as permitted sender)
MIME-Version: 1.0
Sender: saint.ack@gmail.com
In-Reply-To: 
 <CAOcnVr3qRH9i3mEufrdVEmu57JzJfg7taDni0Np2Ng3r=Kjb3g@mail.gmail.com>
References: 
 <E41F4E6CFB766541888FC855399F07C5A27598@szxeml525-mbs.china.huawei.com>
	<D0390CA2-34E0-45B9-AEB3-95A280AECB57@cloudera.com>
	<CADfYSXTObD7H4J4UYfdwK9myZN3oi-01k7tmAbP7RE-=6E6PPw@mail.gmail.com>
	<CAOcnVr3qRH9i3mEufrdVEmu57JzJfg7taDni0Np2Ng3r=Kjb3g@mail.gmail.com>
Date: Mon, 31 Oct 2011 11:13:16 -0700
Message-ID: 
 <CADcMMgHpYdENphxNM_z-Qrt-DT9eFeSBoqw0HnRU=5MQFB1SPQ@mail.gmail.com>
Subject: Re: Hmaster can't start for the latest trunk version
From: Stack <stack@duboce.net>
To: user@hbase.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I backed out hbase-4680.  I made HBASE-4708 to backout the safemode
parts of hbase-4510.  Any chance of a patch Harsh?
Thanks,
St.Ack

On Mon, Oct 31, 2011 at 1:24 AM, Harsh J <harsh@cloudera.com> wrote:
> Gary,
>
> We can revert for now, yes. Todd had fixed the constant name change
> issue earlier, so it should be OK to revert and switch to a decided
> API later. I think that should be fine!
>
> On Mon, Oct 31, 2011 at 1:28 PM, Gary Helmling <ghelmling@gmail.com> wrot=
e:
>> Yes, HBASE-4510 broke running on one set of conditions, now the "fix"
>> in HBASE-4680 seems to have broken another.
>>
>> Are the safe mode related changes from HBASE-4510 really necessary
>> right now? =A0Would it be possible to wait for HDFS-2413, when we have a
>> real API for checking safe mode? =A0Or do we absolutely need the change
>> in safe mode checking to run on 0.23? =A0The previous version of the
>> check at least did not have these issues. =A0If we don't strictly need
>> that change, I'd be in favor of reverting both HBASE-4680 and the
>> safe-mode related bits from HBASE-4510.
>>
>>
>> On Sun, Oct 30, 2011 at 9:44 PM, Harsh J <harsh@cloudera.com> wrote:
>>> Hi Gaojinchao,
>>>
>>> -user (bcc)
>>> +dev
>>>
>>> This appears to be due to https://issues.apache.org/jira/browse/HBASE-4=
680 (and also HBASE-4510 which sourced the whole issue), and is caused by t=
he fact that /hbase doesn't exist yet when you first start it up. I've file=
d https://issues.apache.org/jira/browse/HBASE-4705 for this.
>>>
>>> Workaround may be to "sudo -u hbase-user hadoop dfs -mkdir /hbase" befo=
re starting, for now.
>>>
>>> On 31-Oct-2011, at 9:42 AM, Gaojinchao wrote:
>>>
>>>> The latest trunk version.
>>>> Throw this logs:
>>>> 2011-10-31 00:09:09,549 FATAL org.apache.hadoop.hbase.master.HMaster: =
Unhandled exception. Starting shutdown.
>>>> java.io.FileNotFoundException: File does not exist: hdfs://C3S31:9000/=
hbase
>>>> =A0 =A0 =A0 =A0 at org.apache.hadoop.hdfs.DistributedFileSystem.getFil=
eStatus(DistributedFileSystem.java:731)
>>>> =A0 =A0 =A0 =A0 at org.apache.hadoop.hbase.util.FSUtils.isInSafeMode(F=
SUtils.java:163)
>>>> =A0 =A0 =A0 =A0 at org.apache.hadoop.hbase.util.FSUtils.waitOnSafeMode=
(FSUtils.java:458)
>>>> =A0 =A0 =A0 =A0 at org.apache.hadoop.hbase.master.MasterFileSystem.che=
ckRootDir(MasterFileSystem.java:301)
>>>> =A0 =A0 =A0 =A0 at org.apache.hadoop.hbase.master.MasterFileSystem.cre=
ateInitialFileSystemLayout(MasterFileSystem.java:127)
>>>> =A0 =A0 =A0 =A0 at org.apache.hadoop.hbase.master.MasterFileSystem.<in=
it>(MasterFileSystem.java:112)
>>>> =A0 =A0 =A0 =A0 at org.apache.hadoop.hbase.master.HMaster.finishInitia=
lization(HMaster.java:426)
>>>> =A0 =A0 =A0 =A0 at org.apache.hadoop.hbase.master.HMaster.run(HMaster.=
java:309)
>>>> =A0 =A0 =A0 =A0 at java.lang.Thread.run(Thread.java:662)
>>>> 2011-10-31 00:09:09,551 INFO org.apache.hadoop.hbase.master.HMaster: A=
borting
>>>> 2011-10-31 00:09:09,551 DEBUG org.apache.hadoop.hbase.master.HMaster: =
Stopping service threads
>>>
>>>
>>
>
>
>
> --
> Harsh J
>