[
https://issues.apache.org/jira/browse/HBASE-5959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13276254#comment-13276254
]
Elliott Clark commented on HBASE-5959:
--------------------------------------
And I didn't move the getTopBlockLocations into a helper as this is already a
big enough patch and I wanted to keep the impact to a minimum. If this gets
accepted i'll be filing tickets to add region load cost function (region load
seems broken right now i'm looking into it), and to refactor
getTopBlockLocations.
Assuming the highest cost or the lowest cost for things has no functional
difference. However when/if region load cost functions are added assuming the
worst would not work, so I think it's better to start now with always assuming
the best cost unless it can be proven otherwise.
Other than that yes I believe all of the issues were addressed by what is up on
phabricator.
> Add other load balancers
> ------------------------
>
> Key: HBASE-5959
> URL: https://issues.apache.org/jira/browse/HBASE-5959
> Project: HBase
> Issue Type: New Feature
> Components: master
> Affects Versions: 0.96.0
> Reporter: Elliott Clark
> Assignee: Elliott Clark
> Attachments: HBASE-5959-0.patch, HBASE-5959-1.patch,
> HBASE-5959-2.patch, HBASE-5959-3.patch, HBASE-5959-6.patch,
> HBASE-5959-7.patch, HBASE-5959.D3189.1.patch, HBASE-5959.D3189.2.patch,
> HBASE-5959.D3189.3.patch, HBASE-5959.D3189.4.patch
>
>
> Now that balancers are pluggable we should give some options.b
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
