[
https://issues.apache.org/jira/browse/HBASE-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-3676:
--------------------------
Attachment: hbase-3676-server-mgr.txt
It turns out that ServerManager.processRegionServerAllsWell() is doing server
info refresh.
This patch removes the new method in AssignmentManager and adds the following
method to ServerManager:
{code}
HServerLoad getLoad(String serverName) {
{code}
so that server load is accessible to AssignmentManager
> Update region server load for AssignmentManager through regionServerReport()
> ----------------------------------------------------------------------------
>
> Key: HBASE-3676
> URL: https://issues.apache.org/jira/browse/HBASE-3676
> Project: HBase
> Issue Type: Improvement
> Reporter: Ted Yu
> Assignee: Ted Yu
> Fix For: 0.92.0
>
> Attachments: hbase-3676-server-mgr.txt, hbase-3676.txt
>
>
> Currently the following method only calls serverManager.regionServerReport():
> public HMsg [] regionServerReport(HServerInfo serverInfo, HMsg msgs[],
> HRegionInfo[] mostLoadedRegions)
> This means AssignmentManager doesn't have valid server load information.
> The following method would be added to AssignmentManager:
> public void regionServerReport(HServerInfo serverInfo, HRegionInfo[]
> mostLoadedRegions)
> For HBASE-1502, we would figure out how to store load information through zk.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
