[
https://issues.apache.org/jira/browse/CASSANDRA-5394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis resolved CASSANDRA-5394.
---------------------------------------
Resolution: Won't Fix
One of our long-standing design goals is, "don't require read before write."
But strict quota check before write -- where Cassandra rejects over-quota
writes at insert time -- would effectively require this, since I don't know if
inserting record X will increase my space used, unless I check and see if X
already exists, and if so, what the space-used delta would be.
You can achieve probably "good enough" checking by summing sstable sizes and
disabling writes at the application level if it's over quota. You can do this
with the existing Metrics that Cassandra exposes.
> Allow assigning disk quotas by keyspace
> ---------------------------------------
>
> Key: CASSANDRA-5394
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5394
> Project: Cassandra
> Issue Type: New Feature
> Reporter: J.B. Langston
> Priority: Minor
>
> A customer is requesting this. They are implementing a multi-tenant Cassandra
> Service offering. They want to limit the amount of diskspace that a user or
> application can consume. They would also want to be able to modify the quota
> after the keyspace is set up.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
