[
https://issues.apache.org/jira/browse/HBASE-16999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser updated HBASE-16999:
-------------------------------
Attachment: HBASE-16999-HBASE-16961.001.patch
.001 Landing a patch for now (need to get outstanding patches rebased on the
feature branch).
For an initial implementation, I went the easy route of just using a column in
the {{hbase:quota}} table to persist violation state for a table. The Master is
the only entity to update this table and RegionServers periodically
(configurable) read the quota table and update their current state. This
results in a very simple implementation to understand with similar bounds on
reaction time to quota violation policy changes.
> [Master] Inform RegionServers on size quota violations
> ------------------------------------------------------
>
> Key: HBASE-16999
> URL: https://issues.apache.org/jira/browse/HBASE-16999
> Project: HBase
> Issue Type: Sub-task
> Reporter: Josh Elser
> Assignee: Josh Elser
> Attachments: HBASE-16999-HBASE-16961.001.patch
>
>
> The Master, after computing the total usage across all regionservers, needs
> to inform the RegionServers about tables that need to change violation policy
> enforcement (enable or disable enforcement).
> RPC, ZK, or ProcV2's notification bus are some examples of ways this could be
> implemented.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
