hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Bishop <jbishop....@gmail.com>
Subject more regionservers does not improve performance
Date Fri, 12 Oct 2012 00:08:13 GMT

I am running a MR job with 40 simultaneous mappers, each of which does puts
to HBase. I have ganged up the puts into groups of 1000 (this seems to help
quite a bit) and also made sure that the table is pre-split into 100
regions, and that the row keys are randomized using MD5 hashing.

My cluster size is 10, and I am allowing 4 mappers per tasktracker.

In my MR job I know that the mappers are able to generate puts much faster
than the puts can be handled in hbase. In other words if I let the mappers
run without doing hbase puts then everything scales as you would expect
with the number of mappers created. It is the hbase puts which seem to be
the bottleneck.

What is strange is that I do not get much run time improvement by
increasing the number regionservers beyond about 4. Indeed, it seems that
the system runs slower with 8 regionservers than with 4.

I have added the following in hbase-env.sh hoping this would help... (from
the book HBase in Action)

export HBASE_OPTS="-Xmx8g"
export HBASE_REGIONSERVER_OPTS="-Xmx8g -Xms8g -Xmn128m -XX:+UseParNewGC
-XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=70"

# Uncomment below to enable java garbage collection logging in the .out
export HBASE_OPTS="${HBASE_OPTS} -verbose:gc -XX:+PrintGCDetails
-XX:+PrintGCDateStamps -Xloggc:${HBASE_HOME}/logs/gc-hbase.log"

Monitoring hbase through the web ui I see that there are pauses for
flushing, which seems to run pretty quickly, and for compacting, which
seems to take somewhat longer.

Any advice for making this run faster would be greatly appreciated.
Currently I am looking into installing Ganglia to better monitory my
cluster, but yet to have that running.

I suspect an I/O issue as the regionservers do not seem terribly loaded.



  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message