[
https://issues.apache.org/jira/browse/CASSANDRA-14499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16506748#comment-16506748
]
Jeff Jirsa commented on CASSANDRA-14499:
----------------------------------------
1) disabling gosspi alone is insufficient, also need to disable native
2) recovery is likely some combination of compactions and host replacement
3) still not sure I buy the argument that it’s wrong to serve reads in this
case - it may be true that some table is getting out of sync, but that doesn’t
mean every table is, and we already have a mechanism to deal with nodes that
can serve reads but not writes (speculating on the read repair). If you don’t
serve reads either, than any GC pause will be guaranteed to impact client
request latency as we can’t soeculate around it in the common rf=3 case.
> 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
