[
https://issues.apache.org/jira/browse/HBASE-3943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13043436#comment-13043436
]
Ted Yu commented on HBASE-3943:
-------------------------------
>From Schubert:
{noformat}
In my use case, the region-store size is aggresively set to be very large (such
as 1GB, even 10GB), then, the time of compaction would take tens of minutes
(e.g. 30 minutes).
hbase.regionserver.msginterval=3000, it is the default value.
{noformat}
The benefit of passing compaction status through RegionLoad is that load
balancer wouldn't interrupt a half hour compaction 5 minutes after it starts
(default value of hbase.balancer.period, some users make it longer to reduce
impact of region reassignment).
There is still a chance that compaction is interrupted 3 seconds after it
starts, but the cost is much lower than the above scenario.
> Propagate compaction status from HRegion to HServerLoad.RegionLoad
> ------------------------------------------------------------------
>
> Key: HBASE-3943
> URL: https://issues.apache.org/jira/browse/HBASE-3943
> Project: HBase
> Issue Type: Bug
> Components: master, regionserver
> Reporter: Ted Yu
> Assignee: Ted Yu
>
> Load balancer works with HRegionInfo. However, compaction status is contained
> in HRegion.WriteState
> Users reported the following (Schubert Zhang):
> 1. A region have many files, the compacting takes long time.
> 2. But the balancer (default 5 minutes) close and move this region to
> another server.
> 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.
> We need to propagate compaction status to HServerLoad.RegionLoad so that load
> balancer doesn't move the region which is being compacted.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
