[jira] [Updated] (HBASE-5737) Minor Improvements related to balancer.

["ramkrishna.s.vasudevan (Updated) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-5737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ramkrishna.s.vasudevan updated HBASE-5737:
------------------------------------------

    Summary: Minor Improvements related to balancer.  (was: Use a treemap instead of hashmap in in AM.getAssignmentByTable used in balancer)

There are few more changes that we can do here
-> Currently two different balancer objects are created in AssignmentManager and HMaster.  Unify them
-> balancer.randomAssignment() is getting called once but based on whether the existingplan is null or if it is a force plan we either use the randomplan or not.
Ideally if we are extending a new balancer then randomAssignment will be called but later the plan given by randomAssignment may not be used. 
                
> 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
>
> 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