hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-3943) Propagate compaction status from HRegion to HServerLoad.RegionLoad
Date Wed, 29 Aug 2012 21:56:08 GMT

     [ https://issues.apache.org/jira/browse/HBASE-3943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Lars Hofhansl resolved HBASE-3943.

    Resolution: Duplicate

Closing as dup of HBASE-3945, since that was suggested as the right approach to fix this.
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message