Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 19 Feb 2016 15:16:18 +0000 (UTC)
From: "Aleksey Yeschenko (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12939988.1455751444000.94106.1455894978073@Atlassian.JIRA>
In-Reply-To: <JIRA.12939988.1455751444000@Atlassian.JIRA>
References: <JIRA.12939988.1455751444000@Atlassian.JIRA>
 <JIRA.12939988.1455751444230@arcas>
Subject: [jira] [Updated] (CASSANDRA-11179) Parallel cleanup can lead to
 disk space exhaustion
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-11179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksey Yeschenko updated CASSANDRA-11179:
------------------------------------------
    Issue Type: Improvement  (was: Bug)

> Parallel cleanup can lead to disk space exhaustion
> --------------------------------------------------
>
>                 Key: CASSANDRA-11179
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11179
>             Project: Cassandra
>          Issue Type: Improvement
>          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)