[
https://issues.apache.org/jira/browse/HBASE-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923151#action_12923151
]
Andrew Nguyen commented on HBASE-2826:
--------------------------------------
So, I was getting a similar error (EOFException) that ended up having a
different cause...
I was using Cloudera's CDH3b3 release of Hadoop but pulled the Apache dev
release of HBase instead of Cloudera's. I had attempted to tweak the hostname
and port given James' experience. This didn't seem to help at all so after some
help on IRC from JD, we figured it out after looking at the namenode logs which
indicated an incorrect header or version mismatch...
Here's my stack trace from the HBase master log (also at
http://pastebin.com/4zgygvpu):
{quote}
2010-10-20 09:33:11,180 INFO org.apache.hadoop.hbase.ipc.HBaseRpcMetrics:
Initializing RPC Metrics with hostName=HMaster, port=60000
2010-10-20 09:33:11,551 ERROR org.apache.hadoop.hbase.master.HMaster: Failed to
start master
java.lang.RuntimeException: Failed construction of Master: class
org.apache.hadoop.hbase.master.HMasterCall to master-local/127.0.0.1:8020
failed on local exception: java.io.EOFException
at org.apache.hadoop.hbase.master.HMaster.constructMaster(HMaster.java:1232)
at org.apache.hadoop.hbase.master.HMaster.doMain(HMaster.java:1338)
at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:1389)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at org.apache.hadoop.hbase.master.HMaster.constructMaster(HMaster.java:1230)
... 2 more
Caused by: java.io.IOException: Call to master-local/127.0.0.1:8020 failed on
local exception: java.io.EOFException
at org.apache.hadoop.ipc.Client.wrapException(Client.java:775)
at org.apache.hadoop.ipc.Client.call(Client.java:743)
at org.apache.hadoop.ipc.RPC$Invoker.invoke(RPC.java:220)
at $Proxy0.getProtocolVersion(Unknown Source)
at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:359)
at org.apache.hadoop.hdfs.DFSClient.createRPCNamenode(DFSClient.java:112)
at org.apache.hadoop.hdfs.DFSClient.<init>(DFSClient.java:213)
at org.apache.hadoop.hdfs.DFSClient.<init>(DFSClient.java:176)
at
org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:82)
at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:1378)
at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:66)
at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:1390)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:196)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:95)
at org.apache.hadoop.hbase.master.HMaster.<init>(HMaster.java:217)
... 7 more
Caused by: java.io.EOFException
at java.io.DataInputStream.readInt(DataInputStream.java:375)
at org.apache.hadoop.ipc.Client$Connection.receiveResponse(Client.java:501)
at org.apache.hadoop.ipc.Client$Connection.run(Client.java:446)
{quote}
I was using hadoop-0.20.2+737 from Cloudera and hbase-0.89.20100924 instead of
the appropriate 20100924+28 from Cloudera.
So, while this wasn't a result of the hbase.rootdir being incorrect, it is an
unhelpful exception...
> Unhelpful exception from Client on HBase master startup when hbase.rootdir is
> incorrect.
> ----------------------------------------------------------------------------------------
>
> Key: HBASE-2826
> URL: https://issues.apache.org/jira/browse/HBASE-2826
> Project: HBase
> Issue Type: Improvement
> Components: ipc
> Affects Versions: 0.90.0
> Environment: Ubuntu Karmic, using Cloudera distribution karmic-cdh3.
> The exact hbase version is 0.89.20100621+17.
> Reporter: James Cockrill
> Priority: Minor
>
> As per [email protected] thread:
> http://mail-archives.apache.org/mod_mbox/hbase-user/201007.mbox/%[email protected]%3e
> I setup HBase (and as such, Zookeeper) on Ubuntu Karmic using the Cloudera
> Karmic CDH3 distribution. Zookeeper has installed fine, however when it comes
> to starting an hbase master, it falls over with the following exception:
> (stack trace summarised to last bit)
> Caused by: java.io.EOFException
> at java.io.DataInputStream.readInt(DataInputStream.java:375)
> at org.apache.hadoop.ipc.Client$Connection.receiveResponse(Client.java:508)
> at org.apache.hadoop.ipc.Client$Connection.run(Client.java:446)
> The cause was that the hbase.rootdir was incorrectly set to
> hdfs://master:50071/hbase, when it should have been set to port 50070. After
> remedying this hbase master started fine.
> I was asked to raise this as a JIRA to investigate the possibility of
> improving the handling of the EOFException to perhaps indicate more clearly
> to the user that an incorrect address has been specified for the rootdir,
> rather than the very unclear statement above.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
