[jira] [Commented] (CASSANDRA-16800) Abort repairs whose streaming jobs will push disk usage over a configurable threshold

["Brandon Williams (Jira)" <ji...@apache.org>]

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

Brandon Williams commented on CASSANDRA-16800:
----------------------------------------------

Just pointing out this is probably a little bit tricky in the case of multiple data mounts.

> Abort repairs whose streaming jobs will push disk usage over a configurable threshold
> -------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-16800
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16800
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Consistency/Repair, Consistency/Streaming
>            Reporter: Caleb Rackliffe
>            Priority: Normal
>             Fix For: 4.x
>
>
> When nodes are out of sync, it is possible to get into a situation where streaming from repairs sends us to 100% disk usage (from a starting point of 20% even, in matter of hours). Since we know the size of the data we're going to stream over, and how much disk space is left, we should just fail the streaming instead of causing flush issues on memtables/commitlog/etc. as we approach that point.
> Perhaps it would make sense to have a configurable threshold of say 90% disk usage over which we won't accept more streams.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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