I still get the same error.
This is the contents of the configuration as it is set right before
calling "new
HBaseAdmin(getConfiguration())":
key :hbase.auth.token.max.lifetime
value :60480
key :hbase.thrift.maxQueuedRequests
value :1000
key :io.seqfile.compress.blocksize
value :100
key :
Do you have a local zookeeper running? Telnet localhost 2181 connect to
anything?
Obviously we run 0.94 with no security setup with no problem. Hence looking for
basic setup problems.
- Andy
On Jun 2, 2012, at 1:20 PM, Amit Sela wrote:
> I still get the same error.
>
> This is the cont
A scan should *never* should you expired cells (unless you're doing a "raw"
scan).
If cells haven't been collected, yet, they'll be filtered by the scan. In any
case the expired cells are not returned by the scan.
Can you tell us more details?
The scan code, the timestamps you get, a describe
How are you setting up your M/R jobs?
A while ago (0.92 I think) I added the necessary protobuf jars to the jar
dependencies in HBase's TableMapReduceUtil.
-- Lars
From: Amit Sela
To: user@hbase.apache.org
Sent: Tuesday, May 29, 2012 8:39 AM
Subject: Re: jav
Hi there, I think you probably want to look at thisŠ
Hbase catalog metadataŠ
http://hbase.apache.org/book.html#arch.catalog
How data is stored internallyŠ
http://hbase.apache.org/book.html#regions.arch
Lots of versioning description hereŠ
http://hbase.apache.org/book.html#datamodel
Long s
Related to "when does compaction actually occur?", although the original
question was about the web UI you might also want to see this...
http://hbase.apache.org/book.html#regions.arch
Š for an overview of the compaction file-selection algorithm.
On 6/2/12 8:42 AM, "lars hofhansl" wrote:
>
I don't know about a local zookeeper running.
I'm trying to run a test that extends HBaseTestingUtils.
It worked fine with the old versions when it extended HBaseClusterTestCase.
Since it is deprecated (also same for HBaseTestCase) I adjusted the test a
little bit (things like cong, fs, dfs etc.. b
If you want to get into the really nitty gritty I found Lars' presentation
really insightful.
http://www.hbasecon.com/sessions/learning-hbase-internals/
On Sat, Jun 2, 2012 at 6:13 AM, Doug Meil wrote:
>
> Hi there, I think you probably want to look at thisŠ
>
> Hbase catalog metadataŠ
>
> http:
It's highly likely you are not starting up zookeeper at all then. The security
warning is a red herring. I filed a zookeeper issue to change the log level
from warn to info so it doesn't send folks like yourself down the wrong path.
I'd advise cloning one of the working 0.94 tests that spins u
Ok, I'll try ti raise the value of this timeout and see what happens
thanks
On 6/1/12 5:32 PM, N Keywal wrote:
Yes, this is the balance process (as its name says: keeps the cluster
balanced), and it's not related to the process of looking after dead
nodes.
The nodes are monitored by ZooKeeper,
I've checked and my timeout is already set to 1200 seconds !!!
Ok if the information used for adding a node to the delete list is not
correlated to the loadbalancer I forget this lead ...
On 6/1/12 5:32 PM, N Keywal wrote:
Yes, this is the balance process (as its name says: keeps the cluster
11 matches
Mail list logo
