Re: Need Help on hbase error: The znode for the -ROOT- region doesn't exist!

2013-08-30 Thread Ted Yu
-ROOT- table is gone in 0.95 / 0.96 Looks like newer release of asynchbase is needed which can communicate with 0.96 cluster. Cheers On Fri, Aug 30, 2013 at 4:44 PM, S. Zhou wrote: > I wrote a java program which connects to hbase (I am using asynchbase). > At this time > hbase/hadoop are all

Re: Need Help on hbase error: The znode for the -ROOT- region doesn't exist!

2013-08-30 Thread Mohammad Tariq
Hello there, Looks like some problem with RS holding the -ROOT-. Please make sure it's up and running. Showing us the logs would be helpful. Warm Regards, Tariq cloudfront.blogspot.com On Sat, Aug 31, 2013 at 5:14 AM, S. Zhou wrote: > I wrote a java program which connects to hbase (I am using

Re: where to download 0.95.1-hadoop1 jar file using Maven?

2013-08-30 Thread S. Zhou
Ted, do you have any public maven repository to download hbase client with version hbase-0.95.1-hadoop1? I am kind of surprised that it becomes an issue. From: S. Zhou To: "user@hbase.apache.org" Sent: Thursday, August 15, 2013 8:18 PM Subject: Re: where to

Need Help on hbase error: The znode for the -ROOT- region doesn't exist!

2013-08-30 Thread S. Zhou
I wrote a java program which connects to hbase (I am using asynchbase).  At this time hbase/hadoop are all running on my local dev box as pseudo cluster. I believe hbase/hadoop are all setup correctly since I can create hbase tables, update hbase tables, run MR jobs etc. The problem is: when

Re: where to download 0.95.1-hadoop1 jar file using Maven?

2013-08-30 Thread S. Zhou
Stack, for your following comments: I tried to download from maven central but also failed We also just put out a 0.95.2.  It looks like I actually 'released' the maven artifacts.  You could try these?  Our 0.95.1 maven release was incorrect anyways, if you wanted to use hadoop2. _

Re: Coprocessor concurrency

2013-08-30 Thread Kiru Pakkirisamy
Vlad, I am running in separate processes. But I think I found at least part of the problem. It is the HTable connection setup that is affecting it If I setup all the connections in all the processes for all the tables then and then call the endpoints it goes through ok. At least for the example b

RE: Coprocessor concurrency

2013-08-30 Thread Vladimir Rodionov
Can you check RS thread stack traces during your test? If there are some concurrency/contention issues they will pop up in a stack traces. Also, make sure that you run your client apps in a separate processes. Best regards, Vladimir Rodionov Principal Platform Engineer Carrier IQ, www.carrieriq.c

RE: Coprocessor concurrency

2013-08-30 Thread Vladimir Rodionov
RS handler count 800 is an overkill. Best regards, Vladimir Rodionov Principal Platform Engineer Carrier IQ, www.carrieriq.com e-mail: vrodio...@carrieriq.com From: Vladimir Rodionov Sent: Friday, August 30, 2013 12:34 PM To: user@hbase.apache.org; Kiru P

Running an example from hbase book

2013-08-30 Thread jamal sasha
Hi, I am trying to run this example: https://github.com/larsgeorge/hbase-book ch07 But it throws this error: ava.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.hadoop.util.ReflectionUtils.newInstance(ReflectionUtils.java:115) at org.apache.hadoop.mapred.MapTask.ru

Re: Using HBase timestamps as natural versioning

2013-08-30 Thread Ted Yu
Is your ID fixed length or variable length ? If the length is fixed, you can specify ID/0 as the start row in scan. Cheers On Fri, Aug 30, 2013 at 5:42 AM, Henning Blohm wrote: > Was gone for a few days. Sorry for not getting back to this until now. And > thanks for adding to the discussion! >

Re: Using HBase timestamps as natural versioning

2013-08-30 Thread Henning Blohm
Was gone for a few days. Sorry for not getting back to this until now. And thanks for adding to the discussion! The time used in the timestamp is the "natural" time (in ms resolution) as far as known. I.e. in the end it is of course some machine time, but the trigger to choose it is some human

Coprocessor concurrency

2013-08-30 Thread Kiru Pakkirisamy
See below a null endpoint which takes 60-70msec on my 4 node ec2 cluster for a table with 45 regions. When I run 64 concurrent clients for this the latency jumps to 3000-3700 msec. (zookeeper maxClientCnxs is set to 0 (unlimited) and hbase regionserver handler count is 800). I hope I am not miss

Re: experiencing high latency for few reads in HBase

2013-08-30 Thread Kiru Pakkirisamy
I did check GC earlier. Not much . About .0x seconds. I think there is lock/contention issue. 0.94.11 is also more stable compared to 0.94.10. With 64 concurrent clients, 0.94.10 one regionserver or other will crash. Regards, - kiru From: Adrien Mogenet To: us