[
https://issues.apache.org/jira/browse/CASSANDRA-11179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tyler Hobbs updated CASSANDRA-11179:
------------------------------------
Description:
In CASSANDRA-5547, we made cleanup (among other things) run in parallel across
multiple sstables. There have been reports on IRC of this leading to disk
space exhaustion, because multiple sstables are (almost entirely) rewritten at
the same time. This seems particularly problematic because cleanup is
frequently run after a cluster is expanded due to low disk space.
I'm not really familiar with how we perform free disk space checks now, but it
sounds like we can make some improvements here. It would be good to reduce the
concurrency of cleanup operations if there isn't enough free disk space to
support this.
was:
In CASSANDRA-5366, we made cleanup (among other things) run in parallel across
multiple sstables. There have been reports on IRC of this leading to disk
space exhaustion, because multiple sstables are (almost entirely) rewritten at
the same time. This seems particularly problematic because cleanup is
frequently run after a cluster is expanded due to low disk space.
I'm not really familiar with how we perform free disk space checks now, but it
sounds like we can make some improvements here. It would be good to reduce the
concurrency of cleanup operations if there isn't enough free disk space to
support this.
> Parallel cleanup can lead to disk space exhaustion
> --------------------------------------------------
>
> Key: CASSANDRA-11179
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11179
> Project: Cassandra
> Issue Type: Bug
> Components: Compaction, Tools
> Reporter: Tyler Hobbs
>
> In CASSANDRA-5547, we made cleanup (among other things) run in parallel
> across multiple sstables. There have been reports on IRC of this leading to
> disk space exhaustion, because multiple sstables are (almost entirely)
> rewritten at the same time. This seems particularly problematic because
> cleanup is frequently run after a cluster is expanded due to low disk space.
> I'm not really familiar with how we perform free disk space checks now, but
> it sounds like we can make some improvements here. It would be good to
> reduce the concurrency of cleanup operations if there isn't enough free disk
> space to support this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
