You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hbase.apache.org by Gaojinchao <ga...@huawei.com> on 2011/10/31 05:12:39 UTC
Hmaster can't start for the latest trunk version
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
at org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:731)
at org.apache.hadoop.hbase.util.FSUtils.isInSafeMode(FSUtils.java:163)
at org.apache.hadoop.hbase.util.FSUtils.waitOnSafeMode(FSUtils.java:458)
at org.apache.hadoop.hbase.master.MasterFileSystem.checkRootDir(MasterFileSystem.java:301)
at org.apache.hadoop.hbase.master.MasterFileSystem.createInitialFileSystemLayout(MasterFileSystem.java:127)
at org.apache.hadoop.hbase.master.MasterFileSystem.<init>(MasterFileSystem.java:112)
at org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:426)
at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:309)
at java.lang.Thread.run(Thread.java:662)
2011-10-31 00:09:09,551 INFO org.apache.hadoop.hbase.master.HMaster: Aborting
2011-10-31 00:09:09,551 DEBUG org.apache.hadoop.hbase.master.HMaster: Stopping service threads
Re: Hmaster can't start for the latest trunk version
Posted by Stack <st...@duboce.net>.
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 <ha...@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 <gh...@gmail.com> wrote:
>> 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? Would it be possible to wait for HDFS-2413, when we have a
>> real API for checking safe mode? Or do we absolutely need the change
>> in safe mode checking to run on 0.23? The previous version of the
>> check at least did not have these issues. If 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 <ha...@cloudera.com> wrote:
>>> Hi Gaojinchao,
>>>
>>> -user (bcc)
>>> +dev
>>>
>>> This appears to be due to https://issues.apache.org/jira/browse/HBASE-4680 (and also HBASE-4510 which sourced the whole issue), and is caused by the fact that /hbase doesn't exist yet when you first start it up. I've filed https://issues.apache.org/jira/browse/HBASE-4705 for this.
>>>
>>> Workaround may be to "sudo -u hbase-user hadoop dfs -mkdir /hbase" before 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
>>>> at org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:731)
>>>> at org.apache.hadoop.hbase.util.FSUtils.isInSafeMode(FSUtils.java:163)
>>>> at org.apache.hadoop.hbase.util.FSUtils.waitOnSafeMode(FSUtils.java:458)
>>>> at org.apache.hadoop.hbase.master.MasterFileSystem.checkRootDir(MasterFileSystem.java:301)
>>>> at org.apache.hadoop.hbase.master.MasterFileSystem.createInitialFileSystemLayout(MasterFileSystem.java:127)
>>>> at org.apache.hadoop.hbase.master.MasterFileSystem.<init>(MasterFileSystem.java:112)
>>>> at org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:426)
>>>> at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:309)
>>>> at java.lang.Thread.run(Thread.java:662)
>>>> 2011-10-31 00:09:09,551 INFO org.apache.hadoop.hbase.master.HMaster: Aborting
>>>> 2011-10-31 00:09:09,551 DEBUG org.apache.hadoop.hbase.master.HMaster: Stopping service threads
>>>
>>>
>>
>
>
>
> --
> Harsh J
>
Re: Hmaster can't start for the latest trunk version
Posted by Harsh J <ha...@cloudera.com>.
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 <gh...@gmail.com> wrote:
> 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? Would it be possible to wait for HDFS-2413, when we have a
> real API for checking safe mode? Or do we absolutely need the change
> in safe mode checking to run on 0.23? The previous version of the
> check at least did not have these issues. If 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 <ha...@cloudera.com> wrote:
>> Hi Gaojinchao,
>>
>> -user (bcc)
>> +dev
>>
>> This appears to be due to https://issues.apache.org/jira/browse/HBASE-4680 (and also HBASE-4510 which sourced the whole issue), and is caused by the fact that /hbase doesn't exist yet when you first start it up. I've filed https://issues.apache.org/jira/browse/HBASE-4705 for this.
>>
>> Workaround may be to "sudo -u hbase-user hadoop dfs -mkdir /hbase" before 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
>>> at org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:731)
>>> at org.apache.hadoop.hbase.util.FSUtils.isInSafeMode(FSUtils.java:163)
>>> at org.apache.hadoop.hbase.util.FSUtils.waitOnSafeMode(FSUtils.java:458)
>>> at org.apache.hadoop.hbase.master.MasterFileSystem.checkRootDir(MasterFileSystem.java:301)
>>> at org.apache.hadoop.hbase.master.MasterFileSystem.createInitialFileSystemLayout(MasterFileSystem.java:127)
>>> at org.apache.hadoop.hbase.master.MasterFileSystem.<init>(MasterFileSystem.java:112)
>>> at org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:426)
>>> at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:309)
>>> at java.lang.Thread.run(Thread.java:662)
>>> 2011-10-31 00:09:09,551 INFO org.apache.hadoop.hbase.master.HMaster: Aborting
>>> 2011-10-31 00:09:09,551 DEBUG org.apache.hadoop.hbase.master.HMaster: Stopping service threads
>>
>>
>
--
Harsh J
Re: Hmaster can't start for the latest trunk version
Posted by Gary Helmling <gh...@gmail.com>.
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? Would it be possible to wait for HDFS-2413, when we have a
real API for checking safe mode? Or do we absolutely need the change
in safe mode checking to run on 0.23? The previous version of the
check at least did not have these issues. If 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 <ha...@cloudera.com> wrote:
> Hi Gaojinchao,
>
> -user (bcc)
> +dev
>
> This appears to be due to https://issues.apache.org/jira/browse/HBASE-4680 (and also HBASE-4510 which sourced the whole issue), and is caused by the fact that /hbase doesn't exist yet when you first start it up. I've filed https://issues.apache.org/jira/browse/HBASE-4705 for this.
>
> Workaround may be to "sudo -u hbase-user hadoop dfs -mkdir /hbase" before 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
>> at org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:731)
>> at org.apache.hadoop.hbase.util.FSUtils.isInSafeMode(FSUtils.java:163)
>> at org.apache.hadoop.hbase.util.FSUtils.waitOnSafeMode(FSUtils.java:458)
>> at org.apache.hadoop.hbase.master.MasterFileSystem.checkRootDir(MasterFileSystem.java:301)
>> at org.apache.hadoop.hbase.master.MasterFileSystem.createInitialFileSystemLayout(MasterFileSystem.java:127)
>> at org.apache.hadoop.hbase.master.MasterFileSystem.<init>(MasterFileSystem.java:112)
>> at org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:426)
>> at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:309)
>> at java.lang.Thread.run(Thread.java:662)
>> 2011-10-31 00:09:09,551 INFO org.apache.hadoop.hbase.master.HMaster: Aborting
>> 2011-10-31 00:09:09,551 DEBUG org.apache.hadoop.hbase.master.HMaster: Stopping service threads
>
>
Re: Hmaster can't start for the latest trunk version
Posted by Harsh J <ha...@cloudera.com>.
Hi Gaojinchao,
-user (bcc)
+dev
This appears to be due to https://issues.apache.org/jira/browse/HBASE-4680 (and also HBASE-4510 which sourced the whole issue), and is caused by the fact that /hbase doesn't exist yet when you first start it up. I've filed https://issues.apache.org/jira/browse/HBASE-4705 for this.
Workaround may be to "sudo -u hbase-user hadoop dfs -mkdir /hbase" before 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
> at org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:731)
> at org.apache.hadoop.hbase.util.FSUtils.isInSafeMode(FSUtils.java:163)
> at org.apache.hadoop.hbase.util.FSUtils.waitOnSafeMode(FSUtils.java:458)
> at org.apache.hadoop.hbase.master.MasterFileSystem.checkRootDir(MasterFileSystem.java:301)
> at org.apache.hadoop.hbase.master.MasterFileSystem.createInitialFileSystemLayout(MasterFileSystem.java:127)
> at org.apache.hadoop.hbase.master.MasterFileSystem.<init>(MasterFileSystem.java:112)
> at org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:426)
> at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:309)
> at java.lang.Thread.run(Thread.java:662)
> 2011-10-31 00:09:09,551 INFO org.apache.hadoop.hbase.master.HMaster: Aborting
> 2011-10-31 00:09:09,551 DEBUG org.apache.hadoop.hbase.master.HMaster: Stopping service threads