[
https://issues.apache.org/jira/browse/CASSANDRA-14499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16506971#comment-16506971
]
Jeremiah Jordan commented on CASSANDRA-14499:
---------------------------------------------
If one node has reached “full” how likely is it that others are about to as
well? Without monitoring how will an operator know to do something to “fix”
the situation? I’m just not convinced that it’s worth adding the logic and
complications in the rest of the code to allow this feature, which will maybe
add a short bandaid of time before things completely fall over, and possible
just have things fall over early. If you are lucky and one node has enough more
data than other that it hits this first, without other following shortly
behind, you might give a small amount of breathing room for compaction to clean
a little space out, but that is only going to do so much, it won’t fix the
problem. You need to recognize as an operator that your nodes are full and add
more nodes to your cluster, or add more disk space to your cluster.
> 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
