hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dhruba borthakur (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-3679) Provide cost information associated with moving region(s)
Date Tue, 22 Mar 2011 00:44:05 GMT

    [ https://issues.apache.org/jira/browse/HBASE-3679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009495#comment-13009495

dhruba borthakur commented on HBASE-3679:

What would we do in the following case:

We have two region servers A and B in the cluster, A is doing 20K ops/sec while B is doing
5K ops/second. A client is encountering 10 ms latency per call from A while it sees a 30 ms
latency per call from B.

Are we going to move load from A to B or vice-versa?

> Provide cost information associated with moving region(s)
> ---------------------------------------------------------
>                 Key: HBASE-3679
>                 URL: https://issues.apache.org/jira/browse/HBASE-3679
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Ted Yu
> In order for load balancer to make better decision, we need to establish cost model for
moving region(s).
> One factor would be the number of active scanners on a particular region.
> This count is easy to maintain at HRegion level. instantiateInternalScanner() can increment
the counter and RegionScanner.close() would decrement the count.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message