[
https://issues.apache.org/jira/browse/HBASE-3943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042379#comment-13042379
]
stack commented on HBASE-3943:
------------------------------
Are we mixing region schema and region metrics when we add this to HRI Ted?
I'm not a fan of it. And do you think this the way to go? By the time the
balancer goes to act on the info, it'll be stale, don't you think? It seems
like the balancer issue that the boys were complaining off could be addressed
by having the balancer not move regions it just moved in the previous balance
run? Thanks Ted.
> 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
> Attachments: 3943.txt
>
>
> 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
