You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Josh McKenzie (Jira)" <ji...@apache.org> on 2021/10/11 15:09:00 UTC
[jira] [Updated] (CASSANDRA-17032) Allow configuring max allowable
disk usage quota by keyspace
[ https://issues.apache.org/jira/browse/CASSANDRA-17032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh McKenzie updated CASSANDRA-17032:
--------------------------------------
Test and Documentation Plan: Need to add documentation once we've settled on a) whether to include, and b) the shape of the API.
Status: Patch Available (was: Open)
> Allow configuring max allowable disk usage quota by keyspace
> ------------------------------------------------------------
>
> Key: CASSANDRA-17032
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17032
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Other
> Reporter: Josh McKenzie
> Assignee: Josh McKenzie
> Priority: Normal
>
> This is a similar idea (basically identical idea; didn't want to steamroll that old ticket w/an update to description etc) to what was raised and closed in CASSANDRA-5394. In multi-tenant situations it can be very helpful to provide disk quotas per Keyspaces for users.
> We can do this via a low priority background job that periodically checks disk usage and flips a bit on the Keyspaces when it's over as well as reverts it when things settle back down to prevent needing the read-before-write a hard realtime requirement would introduce. While this would of course allow users to "burst" their usage past that limit in the time window, it would still be sufficient for many use-cases.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org