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] [Updated] (HBASE-15511) ClusterStatus should be able to return responses by scope
Date Fri, 11 Aug 2017 05:20:01 GMT

     [ https://issues.apache.org/jira/browse/HBASE-15511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Reid Chan updated HBASE-15511:
------------------------------
    Attachment: HBASE-15511.master.013.patch

set optional fields in Options default value "true"

> 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
>             Fix For: 2.0.0
>
>         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,
HBASE-15511.master.013.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