[
https://issues.apache.org/jira/browse/HBASE-3943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042398#comment-13042398
]
Ted Yu commented on HBASE-3943:
-------------------------------
Thanks for the reminder, Stack.
HRI isn't a proper carrier for compaction status.
HRegionServer.buildServerLoad() has a chance to pass compaction status to
Master. But in trunk, load balancer doesn't have access to HServerLoad
(including RegionLoad).
I agree that if a region was reassigned in round N, it shouldn't be reassigned
again in round N+1, ideally.
I will log another issue for that.
> Propagate compaction status from HRegion to HRegionInfo
> -------------------------------------------------------
>
> 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 HRegionInfo so that load balancer
> doesn't move the region being compacted.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
