Hi Jeff, Apologies for the slow reply, I must've missed the e-mail in the midst of all the others. I've not created one for hbase before, so apologies if I broke any conventions. I filed it under the ipc component as ipc.Client was the last hbase related class in the stack trace before it went off into the java.io wilderness. I've not set an affects version as it's in the 0.89 branch and none of those versions appeared in the list and i've only marked it as a minor improvement as it's hardly a show-stopper and this thread is now appearing in google search results so should be easy to find.
It's this one: https://issues.apache.org/jira/browse/HBASE-2826 Thanks, Jamie On 8 July 2010 01:24, Jeff Hammerbacher <[email protected]> wrote: > Hey James, > > Can you file a JIRA with information about the unhelpful exception message? > I'm on a mission to hunt down common errors with unhelpful exceptions, and > you seem to have discovered one. > > Thanks, > Jeff > > On Tue, Jul 6, 2010 at 5:39 AM, Jamie Cockrill > <[email protected]>wrote: > >> Dear hbase-users, >> >> Further to this, I've been doing a lot of kicking around with the >> config and learned the following: >> >> - You get the same error if a process is listening on that port, that >> is not a HDFS namenode; >> - Although my web front-end for my namenode is on port 50071, it seems >> the namenode itself (i.e. anything that wants hdfs://) is listening on >> 50070. >> >> Having changed my hbase-site.xml to point to 50070 it now seems to >> have started working. Apologies if anyone has wasted any time looking >> at it. This begs the question, why is my namenode web server on a >> different port, but I'll get to that another time. >> >> Many thanks, >> >> James >> >> >> On 6 July 2010 12:19, Jamie Cockrill <[email protected]> wrote: >> > Dear hbase-users, >> > >> > I was wondering if you might be able to help. I am trying to setup >> > HBase (and as such, Zookeeper) on Ubuntu 10.04 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) >> > >> > Its clearly connecting to the HDFS, but it's giving it a strange >> > response. The section above of the trace identifies the hostname that >> > I've specified in the hbase.rootdir property in the hbase-site.xml and >> > also the IP address, which it must have looked up in DNS. For >> > information, that is set to: >> > hdfs://master:50071/hbase. >> > >> > Also, as i'm just evaluating it at this stage, I'm installing >> > Zookeeper and hbase-master on the same machine as the namenode >> > (master). The regionservers will go somewhere else when I get to that >> > stage. >> > >> > My hbase-site.xml was blank (between the configuration tags) and the >> > only things I've added so far are: >> > >> > hbase.cluster.distributed="true" >> > hbase.rootdir="hdfs://master:50071/hbase" >> > hbase.zookeeper.quorum="master" >> > >> > obviously in the <name><value> format of the XML file, without the >> quotes. >> > >> > I'm at a bit of a loss as to what is going on. I've tried a wget to >> > the namenode dfshealth.asp page and that works fine (obviously thats >> > http:// rather than hdfs://). Any pointers on where to look? >> > >> > Many thanks, >> > >> > Jamie >> > >> > I ran a wget to >> > >> >
