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

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

Since the goal isn't to strictly enforce the quota (its ok if its violated but 
once noticed action should be taken) the code isn't invasive. Its a small 
amount of new code with the only change being to schedule the check on optional 
tasks. That being said, if the concern is complexity, one potential place for 
this (and I think it may be better home regardless) is 
[CASSANDRA-14395|https://issues.apache.org/jira/browse/CASSANDRA-14395].

While this may seem like a small bandaid, and there are cases where multiple 
nodes can go down at once, it is exactly meant to give some headroom. This 
headroom makes it considerably easier to get the cluster into a healthy state 
again. 




> 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