Re: Region not initializing in 2.0.0-beta-1

Yeah, definitely watch out what version you built HBase using as that affects the Hadoop jars you get on the classpath. I think I've seen issues using Hadoop 2.7, 2.8, and 3.0 jars with the wrong "server-side" version. One of those cases where you want to get the exact version lining up :)

Re: Region not initializing in 2.0.0-beta-1

Upgrading to hadoop 2.7 worked. Now i have cluster up :) Will try fixing the asynchbase. Thanks guys. On 1 March 2018 at 16:42, sahil aggarwal wrote: > Past that error now on moving to branch-2, getting following this time. > Looks like it doesn't work with hadoop 2.6,

Re: Region not initializing in 2.0.0-beta-1

Past that error now on moving to branch-2, getting following this time. Looks like it doesn't work with hadoop 2.6, should work with 2.7 i guess as it is build with the same. ERROR [regionserver/perf-cosmos-hdn-a-364357:16020] regions erver.HRegionServer: * ABORTING region server

Re: Region not initializing in 2.0.0-beta-1

Thank you for offer of help. Just trying it and talking out loud when problems is a great help. Please try tip of branch-2. It should be beta-2 soon. Tsdb won't work against hbase2. Someone of us needs to fix asynchbase to do reverse scan instead of closestBefore. I filed an issue a while back

Re: Region not initializing in 2.0.0-beta-1

Stack, It didn't work with zookeeper.version=3.4.10 too. If that's the case then will try what Ted suggested i.e trying out 2.0 SNAPSHOT. Moreover, while I am at it can I help you guys with testing anything else that may you guys have in mind or any other grunt work to give you guys more room

Re: Region not initializing in 2.0.0-beta-1

Any progress Sahil? There was an issue fixed where we'd write the clusterid with server zk client but then would have trouble picking it up with the new zk read-only client seen in tests and fixed subsequent to beta-1. This looks like it. Thanks for trying the beta. S On Thu, Feb 22, 2018

Re: Region not initializing in 2.0.0-beta-1

This sounds like something I've seen in the past but was unable to get past. I think I was seeing it when the hbase-shaded-client was on the classpath. Could you see if the presence of that artifact makes a difference one way or another? On 2/22/18 12:52 PM, sahil aggarwal wrote: Yes, it is

Re: Region not initializing in 2.0.0-beta-1

Yes, it is a clean setup. Here are logs on region startup 2018-02-22 22:17:22,259 DEBUG [main] zookeeper.ClientCnxn: zookeeper.disableAutoWatchReset is false 2018-02-22 22:17:22,401 INFO [main-SendThread(perf-zk-1:2181)] zookeeper.ClientCnxn: Opening socket connection to server perf-zk-1/

Re: Region not initializing in 2.0.0-beta-1

Can you show more of the region server log ? Was the cluster started clean (without any data) ? There have been a lot of changes since 2.0.0-beta-1 was released (both in terms of correctness and performance). If possible, please deploy 2.0 SNAPSHOT for further testing. Cheers On Thu, Feb 22,

Region not initializing in 2.0.0-beta-1

Hi, I am trying to get 2.0.0-beta-1 cluster up to do some perf test but not able to get region servers up. Its stuck in initializing state. Looks like it is stuck in getting the hbaseId from zk: jstack says: "regionserver/perf-rs-1/10.32.73.176:16020" #24 prio=5 os_prio=0 tid=0x7f19e45cc000