hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-3679) Provide cost information associated with moving region(s)
Date Mon, 21 Mar 2011 23:35:06 GMT

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

Ted Yu commented on HBASE-3679:
-------------------------------

>From Ryan:
it would make sense to avoid moving regions, so therefore the more
recently a region was moved, the less likely we should move it.

you could imagine a hypothetical perfect 'region move cost' function
that might look like:

F(r) = timeSinceMoved(r) + size(r) + loadAvg(r)

The functions should probably be normalized to [0,1], so the range of
F would be [0,3] with 3 == 'dont move' and 0 == 'move first'.

The goal is to minimize all the F(r[i]) in the moves.



> 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

Mime
View raw message