More details on what I am seeing:
I set the region size back to the default (256MB) and got much better
performance with fewer pauses for compaction. I loaded until I hit about 150
total regions in the table I am loading now (30 per regionserver) and the
set hbase.hregion.max.filesize back up to 1
I'm doing a test now w/o any GZ compression enabled and I am seeing the same
pauses in loading... any more ideas? I will try dropping my region size down
to 256 MB next. Currently I cannot get any sustained writing via thrift for
more than a few seconds before it all pauses.
-chris
On Tue, Jan 1
fault 256m. Have you tested it?
>
> Sandy
>
> > -Original Message-
> > From: Christopher Tarnas [mailto:c...@tarnas.org] On Behalf Of Chris
> Tarnas
> > Sent: Friday, January 07, 2011 23:07
> > To: user@hbase.apache.org
> > Subject: Strange regionse
Hi Stack,
Thanks for taking a look. I think I caught a regionserver compacting:
http://pastebin.com/y9BQaVeJ
http://pastebin.com/ZMxwEX5j
thanks again,
-chris
On Mon, Jan 10, 2011 at 1:52 PM, Stack wrote:
> Odd. Mind thread dumping the regionserver a few times and
> pastebining it during a
Odd. Mind thread dumping the regionserver a few times and
pastebining it during a compaction so we can see where its spending
time? (Your compaction numbers are bad).
St.Ack
On Fri, Jan 7, 2011 at 11:07 PM, Chris Tarnas wrote:
> Thanks in advance for any help. I've been quite pleased with Hba
:07
> To: user@hbase.apache.org
> Subject: Strange regionserver behavior with GZ compression
>
> Thanks in advance for any help. I've been quite pleased with Hbase for this
> current project and until this problem it has worked quite well.
>
> Test cluster setup is CDH3b3 on a 7 nodes:
Thanks in advance for any help. I've been quite pleased with Hbase for this
current project and until this problem it has worked quite well.
Test cluster setup is CDH3b3 on a 7 nodes:
5 data nodes with 48GB RAM, 8 cores, 4 disks,
2 masters with 8 cores, 2 disks 24GB RAM for master/zookeeper/nam
