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

Jordan West commented on CASSANDRA-14499:
-----------------------------------------

Nothing would disallow truncate, although if one node is at quota, is dropping 
all data what is desired? In some use-cases perhaps. Since deletes temporarily 
inflate storage use, for a node level quota I don't think they should be 
allowed (for a keyspace-level quota that would be different perhaps). The 
client also can't be expected to know exactly which keys live on the node(s) 
that are at quota which makes remediation by delete less viable. The most 
likely remediations are adding more nodes or truncation. A correct 
implementation would prevent neither of these. 

I agree that this could/should live in the management process

> node-level disk quota
> ---------------------
>
>                 Key: CASSANDRA-14499
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14499
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Jordan West
>            Assignee: Jordan West
>            Priority: Major
>
> Operators should be able to specify, via YAML, the amount of usable disk 
> space on a node as a percentage of the total available or as an absolute 
> value. If both are specified, the absolute value should take precedence. This 
> allows operators to reserve space available to the database for background 
> tasks -- primarily compaction. When a node reaches its quota, gossip should 
> be disabled to prevent it taking further writes (which would increase the 
> amount of data stored), being involved in reads (which are likely to be more 
> inconsistent over time), or participating in repair (which may increase the 
> amount of space used on the machine). The node re-enables gossip when the 
> amount of data it stores is below the quota.   
> The proposed option differs from {{min_free_space_per_drive_in_mb}}, which 
> reserves some amount of space on each drive that is not usable by the 
> database.  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to