hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thiruvel Thirumoolan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16169) RegionSizeCalculator should not depend on master
Date Wed, 06 Jul 2016 22:04:11 GMT

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

Thiruvel Thirumoolan commented on HBASE-16169:
----------------------------------------------

[~water], Yes, the intention is to add this to the RegionServer API. The difference is that
ServerLoad and all its members come from ClusterStatus (querying master), while mine queries
the RegionServer and takes the Master out of the path.

> 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
>
>         Attachments: HBASE-16169.master.000.patch
>
>
> 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
(v6.3.4#6332)

Mime
View raw message