[
https://issues.apache.org/jira/browse/HBASE-3943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13043907#comment-13043907
]
stack commented on HBASE-3943:
------------------------------
While passing general outline of compaction status on regionserver might make
sense giving a feel for what a cluster is up to, I do not think that it should
be used as a factor balancing. For one the info the regionserver passes will
likely be stale by the time the master goes to act on it (excepting the extreme
case that Schubert outlines above). Better I think is the suggestion above
where we do not move recently balanced regions. That should work for
schubert's case.
> 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
