hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17794) Remove lingering "violation" in favor of the accurate "snapshot"
Date Mon, 22 May 2017 22:20:06 GMT

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

Hudson commented on HBASE-17794:
--------------------------------

FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3059 (See [https://builds.apache.org/job/HBase-Trunk_matrix/3059/])
HBASE-17794 Swap "violation" for "snapshot" where appropriate (elserj: rev a8460b8bad746fc4815845bcaa9740a51bdd3c25)
* (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/quotas/QuotaTableUtil.java
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/quotas/TableQuotaSnapshotStore.java
* (edit) hbase-protocol-shaded/src/main/protobuf/Quota.proto
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/quotas/QuotaObserverChore.java


> Remove lingering "violation" in favor of the accurate "snapshot"
> ----------------------------------------------------------------
>
>                 Key: HBASE-17794
>                 URL: https://issues.apache.org/jira/browse/HBASE-17794
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Trivial
>             Fix For: HBASE-16961
>
>         Attachments: HBASE-17794.001.HBASE-16961.patch
>
>
> Previously, quota violations used to be stored in the quota table. Eventually, I realized
that I needed to actually persist the utilization of each table/NS, not just the violation
state.
> I know there are cases in the code where "violation" is incorrectly describing things
(it should be "snapshot"). Clean these up for clarity.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message