[
https://issues.apache.org/jira/browse/HBASE-16169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15652270#comment-15652270
]
Thiruvel Thirumoolan commented on HBASE-16169:
----------------------------------------------
[~tedyu], I have changed the hbase-protocol-shaded files and have used them.
Should I also change the hbase-protocol files? Since the client would only use
org.apache.hadoop.hbase.RegionLoad, I guess it should be fine? Let me know if
my assumptions are wrong. Thanks!
> Make RegionSizeCalculator scalable
> ----------------------------------
>
> 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,
> HBASE-16169.master.001.patch, HBASE-16169.master.002.patch,
> HBASE-16169.master.003.patch, HBASE-16169.master.004.patch,
> HBASE-16169.master.005.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)
