You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Reid Chan (JIRA)" <ji...@apache.org> on 2016/08/18 17:41:20 UTC

[jira] [Comment Edited] (HBASE-15511) ClusterStatus should be able to return responses by scope

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

Reid Chan edited comment on HBASE-15511 at 8/18/16 5:41 PM:
------------------------------------------------------------

A client can retrieve desired information of ClusterStatus by providing a scope named ClusterInfo.

If ClusterInfo is not provided, all information will be retrieved as original version.

It can be applied to cluster wide, but only after reviewed and with permissions.


was (Author: reidchan):
A client can retrieve desired information of ClusterStatus by providing a scope named ClusterInfo.

If ClusterInfo is not provided, all information will be retrieved as original version.

It can be applied to cluster wide, but only after being reviewed and with permissions.

> 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
>
>
> 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.3.4#6332)