Details
-
Improvement
-
Status: Open
-
Normal
-
Resolution: Unresolved
-
None
-
None
-
Operability
-
Low Hanging Fruit
-
All
-
None
-
Description
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.