Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
HBase >> mail # user >> Slow start of HBase operations with YCSB, possibly because of zookeeper ?


Copy link to this message
-
Re: Slow start of HBase operations with YCSB, possibly because of zookeeper ?
Thanks for sharing, Akshay.

I think the solution should be part of hbase reference guide.

On Fri, Jan 18, 2013 at 7:55 AM, Akshay Singh <[EMAIL PROTECTED]> wrote:

> I found the problem, so I thought I would post it here for future
> reference.
>
> The problem was IPv6 enabled network. Though IPv6 in HDFS (
> HADOOP_OPTS=-Djava.net.preferIPv4Stack=true), and in HBase (
> -Djava.net.preferIPv4Stack=true) was already disabled, but for some of the
> machines in cluster IPv6 was not disabled in kernel (through sysctl).
>
> So hbase was using IPv6 for its services on some of the hosts. So I am
> guessing at start of every workload, HBase tries to resolve AAAA records,
> which eventually times out. And then it resolves to IPv4 address, and thats
> when operations start at normal rate.
>
> On the same note, surprisingly, in one of the host disabling IPv6 through
> sysctl (persisted in sysctl.conf) was not enough to discourage HBase to use
> IPv6 communication. I had to disable IPv6 in grub (default grub cmdline in
> /etc/default/grub) on this host.
>
> After there was *no IPv6 whatsoever* in the cluster, YCSB clients start
> doing operation on HBase immediately.
>
> Thanks,
> Akshay
>
>
>
> ________________________________
>  From: Akshay Singh <[EMAIL PROTECTED]>
> To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> Sent: Tuesday, 15 January 2013 10:36 AM
> Subject: Re: Slow start of HBase operations with YCSB, possibly because of
> zookeeper ?
>
> Thanks Samar.
>
> You are right YCSB writes data to a single table 'usertable', but I see
> very slow operations (in order of 1-2 operations/second) even for
> read/update workload and not only for inserts. So, the region is already
> split in to multiple RS before I start my transaction workload.
>
> And keys are fairly random in YCSB, so I doubt if the slow operations are
> owing to the fact that table is initially limited to one region.
>
> To my knowledge this should have something to do with Zookeeper, as (said
> in the original mail) if I increase the
> "hbase.zookeeper.watcher.sync.connected.wait" (to 10 sec) I dont see the
> exceptions thrown by ZookeeperWatcher, which I see with default value of
> 2s. I have a stand-alone zookeeper instance, to which all RS connects to.
>
> Any other component I should closely monitor ?
>
> Thanks,
> Akshay
>
>
>
> ________________________________
> From: samar kumar <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Sent: Tuesday, 15 January 2013 3:58 AM
> Subject: Re: Slow start of HBase operations with YCSB, possibly because of
> zookeeper ?
>
> YCSB would be writing all data to one table.. So initially when the table
> is small or just created all the writes would go to one RS.. As the table
> grows the Region is split into different RS. The would allow parallel
> writes, if the keys are random and could possibly make the writes faster.
> Samar
>
> On 15/01/13 6:34 AM, "Akshay Singh" <[EMAIL PROTECTED]> wrote:
>
> >
> >Hi hbase users,
> >
> >I am running HBase (on top of HDFS) in
> >distributed mode (on 8 VMs), and things like JPS look fine on all the
> >machines in the cluster. I am also able to run hbase shell and
> >interact with HBase though it. But when I want to benchmark my HBase
> >cluster with YCSB (Yahoo! Cloud System Benchmark,
> >https://github.com/brianfrankcooper/YCSB/) I see this weird problem
> >of slow start of the HBase operations and then picking up later.
> >
> >Basically when I start the YCSB
> >workload from a client machine, I see these problems in chronological
> >order :
> >
> >1) ERROR zookeeper.ZooKeeperWatcher: ZK
> >is null on connection event
> >
> >###########
> >ERROR zookeeper.ZooKeeperWatcher: ZK is
> >null on connection event -- see stack trace for the stack trace when
> >constructor was called on this zkw
> >java.lang.Exception: ZKW CONSTRUCTOR
> >STACK TRACE FOR DEBUGGING
> >at
> >org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher.<init>(ZooKeeperWatcher
> >.java:142)
> >at
> >org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher.<init>(ZooKeeperWatcher
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB