Rohan, The first thing I'd look at is your port: 21818 - the default is 2181 - did you perhaps add the extra "8" in your hbase configuration? Can you query hbase through the shell?
-Matt On Mon, Jul 18, 2011 at 11:51 AM, Rohan Rai <[email protected]> wrote: > Actually I had a question before that. > > How did u manage to make it store > > I keep on getting this > > 2011-07-18 23:04:58,274 [main-SendThread(localhost:**21818)] INFO > org.apache.zookeeper.**ClientCnxn - Opening socket connection to server > localhost/127.0.0.1:21818 > 2011-07-18 23:04:58,275 [main-SendThread(localhost:**21818)] WARN > org.apache.zookeeper.**ClientCnxn - Session 0x0 for server null, > unexpected error, closing socket connection and attempting reconnect > java.net.ConnectException: Connection refused > at sun.nio.ch.SocketChannelImpl.**checkConnect(Native Method) > at > sun.nio.ch.SocketChannelImpl.**finishConnect(**SocketChannelImpl.java:567) > at org.apache.zookeeper.**ClientCnxn$SendThread.run(**ClientCnxn.java: > > > > On Monday 18 July 2011 11:06 PM, Matt Davies wrote: > >> Hello, >> >> Is there a way to specify the zookeeper quorum for a pig job writing out >> to >> HBase using HBaseStorage? For instance, >> >> jobA -> zkquorum 1 >> jobB -> zkquorum 2 >> >> I know that it reads from the hbase configuration files on disk, but I'd >> like the equivalent of setting >> conf.set("hbase.zookeeper.**quorum", "zkquorum1") without recompiling it >> into >> HBaseStorage. >> >> Thanks in advance. >> >> -Matt >> >> > > ______________________________**__ > > The information contained in this communication is intended solely for the > use of the individual or entity to whom it is addressed and others > authorized to receive it. It may contain confidential or legally privileged > information. If you are not the intended recipient you are hereby notified > that any disclosure, copying, distribution or taking any action in reliance > on the contents of this information is strictly prohibited and may be > unlawful. If you have received this communication in error, please notify us > immediately by responding to this email and then delete it from your system. > The firm is neither liable for the proper and complete transmission of the > information contained in this communication nor for any delay in its > receipt. >
