Databases
StackOverflow2013
Postsdbo
POHbase client ConnectionLoss for /hbase error
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHbase client ConnectionLoss for /hbase error
    primarykey
    data
    text
    <p>I'm going completely crazy: </p> <p>Installed Hadoop/Hbase, all is running; </p> <pre><code>/opt/jdk1.6.0_24/bin/jps 23261 ThriftServer 22582 QuorumPeerMain 21969 NameNode 23500 Jps 23021 HRegionServer 22211 TaskTracker 22891 HMaster 22117 SecondaryNameNode 21779 DataNode 22370 Main 22704 JobTracker </code></pre> <p>Pseudo distributed environment. </p> <p>hbase shell </p> <p>is working and coming up with correct results running 'list' and;</p> <pre><code>hbase shell HBase Shell; enter 'help&lt;RETURN&gt;' for list of supported commands. Type "exit&lt;RETURN&gt;" to leave the HBase Shell Version 0.90.1-cdh3u0, r, Fri Mar 25 16:10:51 PDT 2011 hbase(main):001:0&gt; status 1 servers, 0 dead, 8.0000 average load </code></pre> <p>When connecting via ruby &amp; thrift, everything is working fine; we are adding data, it's getting in the system, we can query/scan it. Everything seems fine. </p> <p>However, when connecting with Java:</p> <pre><code>groovy&gt; import org.apache.hadoop.hbase.HBaseConfiguration groovy&gt; import org.apache.hadoop.hbase.client.HBaseAdmin groovy&gt; conf = HBaseConfiguration.create() groovy&gt; conf.set("hbase.master","127.0.0.1:60000"); groovy&gt; hbase = new HBaseAdmin(conf); Exception thrown org.apache.hadoop.hbase.ZooKeeperConnectionException: org.apache.hadoop.hbase.ZooKeeperConnectionException: org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss for /hbase at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.getZooKeeperWatcher(HConnectionManager.java:1000) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.setupZookeeperTrackers(HConnectionManager.java:303) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.&lt;init&gt;(HConnectionManager.java:294) at org.apache.hadoop.hbase.client.HConnectionManager.getConnection(HConnectionManager.java:156) at org.apache.hadoop.hbase.client.HBaseAdmin.&lt;init&gt;(HBaseAdmin.java:84) </code></pre> <p>I've been trying to find the cause, but I really have no clue at all. Everything seems to be correctly installed. </p> <pre><code>netstat -lnp|grep 60000 tcp6 0 0 :::60000 :::* LISTEN 22891/java </code></pre> <p>Looks fine as well. </p> <pre><code># telnet localhost 60000 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. </code></pre> <p>Connects and dies if you type anything + enter (not sure if that's the idea, thrift on 9090 does the same). </p> <p>Can anyone help me? </p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCharlesS
    1. USCharlesS
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHbase client ConnectionLoss for /hbase error
      1. USznetor
      1. VTFavorite
    2. VO
      singulars
      1. POHbase client ConnectionLoss for /hbase error
      1. USNarendra Yadala
      1. VTFavorite
    3. VO
      singulars
      1. POHbase client ConnectionLoss for /hbase error
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload