Mailing-List: contact cassandra-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cassandra-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of rrabah@playdom.com designates
 74.125.149.71 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <a1625f290912031518i79552f45td31f7c9a797007b9@mail.gmail.com>
References: <a1625f290912031518i79552f45td31f7c9a797007b9@mail.gmail.com>
Date: Thu, 3 Dec 2009 18:07:24 -0800
Message-ID: <a1625f290912031807p4a75fbe5i3fc36d41f7711d60@mail.gmail.com>
Subject: Re: Removes increasing disk space usage in Cassandra?
From: Ramzi Rabah <rrabah@playdom.com>
To: cassandra-user@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Looking at jconsole I see a high number of writes when I do removes,
so I am guessing these are tombstones being written? If that's the
case, is the data being removed and replaced by tombstones? and will
they all be deleted eventually when compaction runs?


On Thu, Dec 3, 2009 at 3:18 PM, Ramzi Rabah <rrabah@playdom.com> wrote:
> Hi all,
>
> I ran a test where I inserted about 1.2 Gigabytes worth of data into
> each node of a 4 node cluster.
> I ran a script that first calls a get on each column inserted followed
> by a remove. Since I was basically removing every entry
> I inserted before, I expected that the disk space occupied by the
> nodes will go down and eventually become 0. The disk space
> actually goes up when I do the bulk removes to about 1.8 gigs per
> node. Am I missing something here?
>
> Thanks a lot for your help
> Ray
>