[
https://issues.apache.org/jira/browse/HBASE-8119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630623#comment-13630623
]
Ted Yu commented on HBASE-8119:
-------------------------------
{code}
* @param initialRegionMapping Map of where the regions started.
* @param clusterState Map of ServerName to list of regions.
* @return a double of a cost associated with the proposed
*/
protected double computeCost(Cluster cluster) {
{code}
The first two parameters in javadoc above no longer apply to the method.
You can see the javadoc warning in the most recent QA report, as of this
writing:
https://builds.apache.org/job/PreCommit-HBASE-Build/5297/console
> Optimize StochasticLoadBalancer
> -------------------------------
>
> Key: HBASE-8119
> URL: https://issues.apache.org/jira/browse/HBASE-8119
> Project: HBase
> Issue Type: Bug
> Components: Region Assignment
> Affects Versions: 0.95.0
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Priority: Critical
> Fix For: 0.98.0, 0.95.1
>
> Attachments: hbase-8119_v2.patch, hbase-8119_v3.patch
>
>
> On a 5 node trunk cluster, I ran into a weird problem with
> StochasticLoadBalancer:
> server1 Thu Mar 14 03:42:50 UTC 2013 0.0 33
> server2 Thu Mar 14 03:47:53 UTC 2013 0.0 34
> server3 Thu Mar 14 03:46:53 UTC 2013 465.0 42
> server4 Thu Mar 14 03:47:53 UTC 2013 11455.0 282
> server5 Thu Mar 14 03:47:53 UTC 2013 0.0 34
> Total:5 11920 425
> Notice that server4 has 282 regions, while the others have much less. Plus
> for one table with 260 regions has been super imbalanced:
> {code}
> Regions by Region Server
> Region Server Region Count
> http://server3:60030/ 10
> http://server4:60030/ 250
> {code}
--
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
