hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16961) FileSystem Quotas
Date Mon, 01 May 2017 18:36:04 GMT

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

Josh Elser commented on HBASE-16961:

bq. Well one thing that immediately comes to mind is list_quota_snapshots and list_quota_violations
should have the same output format. The difference is filtering applied to the latter.

Not really, actually. The former is polling the quota table to list the recorded quota "snapshot"
objects. This snapshot includes the space usage, the space limit, and the quota policy (if
the use is greater than the limit).

The latter command (list_quota_violations) is asking a specific regionserver for the list
of quotas that are in violation on that regionserver. The more I think about it, the latter
is just not generally useful for operators (only useful when there is a bug and we are investigating
why some regionserver is not rejecting requests).

Regardless of the usefulness, the extra columns missing on list_quota_violations might be
due to an internal change (RS's used to only see the violation policy or nothing -- they see
the full snapshot now).

> FileSystem Quotas
> -----------------
>                 Key: HBASE-16961
>                 URL: https://issues.apache.org/jira/browse/HBASE-16961
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>         Attachments: hbase-quota-test.sh
> Umbrella issue for tracking the filesystem utilization of HBase data, defining quotas
on that utilization, and enforcement when utilization exceeds the limits of the quota.
> At a high level: we can define quotas on tables and namespaces. Region size is computed
by RegionServers and sent to the Master. The Master inspects the sizes of Regions, rolling
up to table and namespace sizes. Defined quotas in the quota table are evaluated given the
computed sizes, and, for those tables/namespaces violating the quota, RegionServers are informed
to take some action to limit any further filesystem growth by that table/namespace.
> Discuss: https://lists.apache.org/thread.html/66a4b0c3725b5cbdd61dd6111c43847adaeef7b7da5f4cd045df30ef@%3Cdev.hbase.apache.org%3E
> Design Doc: http://home.apache.org/~elserj/hbase/FileSystemQuotasforApacheHBase.pdf or

This message was sent by Atlassian JIRA

View raw message