Re: Major Compaction Strategy

If unchanged, then the region is > considered idle. > > -Original Message- > From: Saad Mufti [mailto:saad.mu...@gmail.com] > Sent: Friday, April 29, 2016 5:37 PM > To: user@hbase.apache.org > Subject: Re: Major Compaction Strategy > > Unfortunately all our tables and re

RE: Major Compaction Strategy

the counts again. If unchanged, then the region is considered idle. -Original Message- From: Saad Mufti [mailto:saad.mu...@gmail.com] Sent: Friday, April 29, 2016 5:37 PM To: user@hbase.apache.org Subject: Re: Major Compaction Strategy Unfortunately all our tables and regions are active 24/7

Re: Major Compaction Strategy

; -Original Message- > From: Saad Mufti [mailto:saad.mu...@gmail.com <javascript:;>] > Sent: Friday, April 29, 2016 1:51 PM > To: user@hbase.apache.org <javascript:;> > Subject: Re: Major Compaction Strategy > > We have more issues now, after testing this in dev, i

RE: Major Compaction Strategy

Try to get code from dev branch. The master and rel_1.1 is on 0.98. -Original Message- From: Ted Yu [mailto:yuzhih...@gmail.com] Sent: Friday, April 29, 2016 5:34 PM To: user@hbase.apache.org Subject: Re: Major Compaction Strategy Interesting. When compiling against hbase 1.1.2, I got

Re: Major Compaction Strategy

plications and the cluster is doing far better > than when using default scheduled MC. > > > -Original Message- > From: Saad Mufti [mailto:saad.mu...@gmail.com] > Sent: Friday, April 29, 2016 1:51 PM > To: user@hbase.apache.org > Subject: Re: Major Compaction Strategy >

RE: Major Compaction Strategy

t 10 hours a day and it has virtually no impact to applications and the cluster is doing far better than when using default scheduled MC. -Original Message- From: Saad Mufti [mailto:saad.mu...@gmail.com] Sent: Friday, April 29, 2016 1:51 PM To: user@hbase.apache.org Subject: Re: Major

Re: Major Compaction Strategy

What I scripted quite easily - we are hitting one major compaction per table at a time (saying also we have much bigger regions than that, and it takes couple of hours per region to compact). We made simple script which is finding region to compact based on some parameters we define (mostly we

Re: Major Compaction Strategy

We have more issues now, after testing this in dev, in our production cluster which has tons of data (60 regions servers and around 7000 regions), we tried to do rolling compaction and most regions that were around 6-7 GB n size were taking 4-5 minutes to finish. Based on this we estimated it

Re: Major Compaction Strategy

Thanks for the pointer. Working like a charm. Saad On Tue, Apr 19, 2016 at 4:01 PM, Ted Yu wrote: > Please use the following method of HBaseAdmin: > > public CompactionState getCompactionStateForRegion(final byte[] > regionName) > > Cheers > > On Tue, Apr 19, 2016

Re: Major Compaction Strategy

Please use the following method of HBaseAdmin: public CompactionState getCompactionStateForRegion(final byte[] regionName) Cheers On Tue, Apr 19, 2016 at 12:56 PM, Saad Mufti wrote: > Hi, > > We have a large HBase 1.x cluster in AWS and have disabled automatic major >

Major Compaction Strategy

Hi, We have a large HBase 1.x cluster in AWS and have disabled automatic major compaction as advised. We were running our own code for compaction daily around midnight which calls HBaseAdmin.majorCompactRegion(byte[] regionName) in a rolling fashion across all regions. But we missed the fact