|| at Jun 1, 2011 at 4:14 am
We have encounter following issue:
1. A region have many files, the compacting takes long time.
2. But the balancer (default 5 minutes) close and move this region to
3. Then, the compacting start again.
4. Then, then balancer close and move it to another server.
Thus, the compacting cannot complete.
Now, we set the balancer interval to 30 minutes to remission this issue.
On Wed, Jun 1, 2011 at 11:02 AM, Stack wrote:
If compacting, don't we interrupt it so we can close and move the
region. You are worried about the compacting work done so far -- you
don't want to lose it? So you are suggesting that a region should be
able to say "No, not now! I'm busy?" (We'd need to distingush between
a balancer 'move' and a move or close for any other region).
On Tue, May 31, 2011 at 7:44 PM, Anty wrote:
When doing balance, Can we take into account the compaction status of
Currently, even the region is doing compaction, it can also be
to response to reassign.
On Sun, May 29, 2011 at 12:57 AM, Schubert Zhang wrote:
Thanks, I think it is HBASE-3373
If the tables are created with pre-split regions, the regions would be
If the tables are created with single region, subsequent write
On Fri, May 20, 2011 at 12:25 AM, Schubert Zhang <firstname.lastname@example.org>
I have a question about HBase balancer.
In release 0.90.x, it seems the balancer only regards the number of regions
and balance these regions into every regionserver.
If we have two tables (A and B) now, each have 100 regions.
Then, a extreme situation is:
RegionsServer1: 100 regions, which all belong to table A
RegionsServer2: 100 regions, which all belong to table B
If my application access table B heavy, the almost all opetations
RegionsServer2, it is not balance.
I have a idea about the balance policy:
(1) Firstly balance for each table
(2) Then, overall balance.