hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Reid Chan (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HBASE-15511) ClusterStatus should be able to return responses by scope
Date Thu, 10 Aug 2017 12:28:00 GMT

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

Reid Chan edited comment on HBASE-15511 at 8/10/17 12:27 PM:
-------------------------------------------------------------

Rebase master branch, and add more detailed info on the deprecated method.


was (Author: reidchan):
Rebase master branch, and add more detailed info on the deprecation method.

> ClusterStatus should be able to return responses by scope
> ---------------------------------------------------------
>
>                 Key: HBASE-15511
>                 URL: https://issues.apache.org/jira/browse/HBASE-15511
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Esteban Gutierrez
>            Assignee: Reid Chan
>         Attachments: HBASE-15511.master.001.patch, HBASE-15511.master.002.patch, HBASE-15511.master.003.patch,
HBASE-15511.master.004.patch, HBASE-15511.master.005.patch, HBASE-15511.master.006.patch,
HBASE-15511.master.007.patch, HBASE-15511.master.008.patch, HBASE-15511.master.009.patch,
HBASE-15511.master.010.patch, HBASE-15511.master.011.patch, HBASE-15511.master.012.patch
>
>
> The current ClusterStatus response returns too much information about the load per region
and replication cluster wide. Sometimes that response can be quite large (10s or 100s of MBs)
and methods like getServerSize() or getRegionsCount() don't really need the full response.
One possibility is to provide a scope (or filter) for the ClusterStatus requests to limit
the response back to the client.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message