Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of dwahler@indeed.com designates
 74.125.82.48 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <54792650.219886.1426544924926.JavaMail.yahoo@mail.yahoo.com>
References: 
 <CACV_4ivNCxfz8DaqPZupe7t=RqiFftAMCf6u8m=ATFkcD9p4hg@mail.gmail.com>
 <54792650.219886.1426544924926.JavaMail.yahoo@mail.yahoo.com>
From: David Wahler <dwahler@indeed.com>
Date: Mon, 16 Mar 2015 17:52:56 -0500
Message-ID: 
 <CACV_4it5YDUrqouUFbTv=muT+U-xXEiOH6xasuYY+R6OrBDAZA@mail.gmail.com>
Subject: Re: Deleted snapshot files filling up /var/lib/cassandra
To: user@cassandra.apache.org, Jan <cnet62@yahoo.com>
Content-Type: text/plain; charset=UTF-8

On Mon, Mar 16, 2015 at 5:28 PM, Jan <cnet62@yahoo.com> wrote:
> David;
>
> all the packaged installations use the /var/lib/cassandra directory.
> Could you check your yaml config files and see if you are using this default
> directory  for backups
>
> May want to change it to a location with more disk space.

We're using the default /var/lib/cassandra as our data directory,
mounted as its own LVM volume. I don't see anything in cassandra.yaml
about a backup directory. There is an "incremental_backups" option
which is set to false.

Increasing the available disk space doesn't really seem like a
solution. We have only about 450MB of live data on the most
heavily-loaded server, and the space taken up by these deleted files
is growing by several GB per day. For now we can work around the
problem by periodically restarting servers to close the file handles,
but that hurts our availability and seems like a hack.