[
https://issues.apache.org/jira/browse/HBASE-5737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252207#comment-13252207
]
stack commented on HBASE-5737:
------------------------------
Ram, the AM#setBalancer is not right? Doesn't AM make a balancer instance of
its own up in its constructor? We should at least remove that. Could we pass
in the load balancer to use into the AM's constructor rather than call a
setBalancer method?
> Minor Improvements related to balancer.
> ---------------------------------------
>
> Key: HBASE-5737
> URL: https://issues.apache.org/jira/browse/HBASE-5737
> Project: HBase
> Issue Type: Improvement
> Components: master
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
> Priority: Minor
> Attachments: HBASE-5737.patch, HBASE-5737_1.patch, HBASE-5737_2.patch
>
>
> Currently in Am.getAssignmentByTable() we use a result map which is currenly
> a hashmap. It could be better if we have a treeMap. Even in
> MetaReader.fullScan we have the treeMap only so that we have the naming order
> maintained. I felt this change could be very useful in cases where we are
> extending the DefaultLoadBalancer.
--
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