hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "li xiang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16169) RegionSizeCalculator should not depend on master
Date Mon, 04 Jul 2016 09:50:10 GMT

    [ https://issues.apache.org/jira/browse/HBASE-16169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15361104#comment-15361104

li xiang commented on HBASE-16169:

Hi Thiruvel, I happened to read this JIRA and it is awesome if it can be implemented.
So do you plan to add the API into HRegionServer? 
Also, ServerLoad.getRegionLoad() seems provide a similar function to return a map of region
name and RegionLoad hosted by the region server. Do you mind elaborating more about your proposal,
what are the differences between the API you are proposing and ServerLoad.getRegionLoad()?

Please correct me if I did not get it correctly.

> RegionSizeCalculator should not depend on master
> ------------------------------------------------
>                 Key: HBASE-16169
>                 URL: https://issues.apache.org/jira/browse/HBASE-16169
>             Project: HBase
>          Issue Type: Sub-task
>          Components: mapreduce, scaling
>            Reporter: Thiruvel Thirumoolan
>            Assignee: Thiruvel Thirumoolan
>             Fix For: 2.0.0, 1.4.0
> RegionSizeCalculator is needed for better split generation of MR jobs. This requires
RegionLoad which can be obtained via ClusterStatus, i.e. accessing Master. We don't want master
to be in this path.
> The proposal is to add an API to the RegionServer that gets RegionLoad of all regions
hosted on it or those of a table if specified. RegionSizeCalculator can use the latter.

This message was sent by Atlassian JIRA

View raw message