[
https://issues.apache.org/jira/browse/CASSANDRA-14499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16506701#comment-16506701
]
Jeff Jirsa commented on CASSANDRA-14499:
----------------------------------------
Not clear to me how you'd do this as gracefully at the OS level as you can at
the cassandra level (by, e.g., blocking writes and inbound streaming).
It's also not clear to me that disabling gossip is the right answer. You can
still serve reads, the coordinator will know if it's out of sync and can
attempt a (now non-blocking and speculating) read repair if necessary. If read
repair is required to meet consistency, we'll fail there, but that's still
likely better than not serving the already consistent read.
> 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
