alibaba / alibaba/node-hbase-client

problem connection [hbase-client] zookeeper watch error: Exception: NO_NODE[-101]

Open
#72 5 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
279
Forks
86
PR merge metrics
No merged PRs in 30d

Description

hi

my config :

hadoop 2.5
hbase : 0.96
zookeeper : 3.4.6

always i have the same problem

[Thu Sep 11 2014 18:11:36 GMT+0200 (CEST)] [worker:19663] [hbase-client] zookeeper watch error: Exception: NO_NODE[-101]
at ConnectionManager.onSocketData (/root/apps/node-hbase/node_modules/hbase-client/node_modules/zookeeper-watcher/node_modules/node-zookeeper-client/lib/ConnectionManager.js:570:35)
at Socket.emit (events.js:95:17)
at Socket. (_stream_readable.js:764:14)
at Socket.emit (events.js:92:17)
at emitReadable_ (_stream_readable.js:426:10)
at emitReadable (_stream_readable.js:422:5)
at readableAddChunk (_stream_readable.js:165:9)
at Socket.Readable.push (_stream_readable.js:127:10)
at TCP.onread (net.js:528:21)

nodefile :

var HBase = require('hbase-client');
var config = {
zookeeperHosts: [
'localhost:2181',
],
zookeeperRoot: '/zookeeper',
};

var client = HBase.create(config);

client.getRow('test', 'row1', ['cf:a'], function (err, row) {
console.log("row");
console.log(row);
console.log("err");
console.log(err);
});

any idea ? thanks

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the supplied nodefile and the ConnectionManager.js location in the stack trace, checking the listed Hadoop, HBase, and ZooKeeper versions and configuration. Reproduce the getRow call and verify whether the watch error persists; the issue does not define a code change or a more precise completion condition.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, nodejs
Domain
database
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.