Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <BANLkTinLU_3tBccAD7CH-A0oFSh_6Ku2fg@mail.gmail.com>
References: <BANLkTikE9Kc6XvACT-OaRW0Q+BXaY7rWZQ@mail.gmail.com>
	<BANLkTinCG_tgqzc1vjvkn+Xv5+BbNXWdjw@mail.gmail.com>
	<BANLkTimVEFi_wCfbiHZCo-i3L9hDRx6T6w@mail.gmail.com>
	<BANLkTinLU_3tBccAD7CH-A0oFSh_6Ku2fg@mail.gmail.com>
Date: Tue, 28 Jun 2011 11:00:09 +0300
Message-ID: <BANLkTimx-7u0gj7j_hkMT6ems6sYxQffPg@mail.gmail.com>
Subject: Re: Truncate introspection
From: David Boxenhorn <david@citypath.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Does drop work in a similar way?

When I drop a CF and add it back with a different schema, it seems to work.

But I notice that in between the drop and adding it back, when the CLI
tells me the CF doesn't exist, the old data is still there.

I've been assuming that this works, but just wanted to make sure...

On Tue, Jun 28, 2011 at 12:56 AM, Jonathan Ellis <jbellis@gmail.com> wrote:
> Each node (independently) has logic that guarantees that any writes
> processed before the truncate, will be wiped out.
>
> This does not mean that each node will wipe out the same data, or even
> that each node will process the truncate (which would result in a
> timedoutexception).
>
> It also does not mean you can't have writes immediately after the
> truncate that would race w/ a "truncate, check for zero sstables"
> procedure.
>
> On Mon, Jun 27, 2011 at 3:35 PM, Ethan Rowe <ethan@the-rowes.com> wrote:
>> If those went to zero, it would certainly tell me something happened. =
=A0:) =A0I
>> guess watching that would be a way of seeing something was going on.
>> Is the truncate itself propagating a ring-wide marker or anything so the=
 CF
>> is logically "empty" before being physically removed? =A0That's the impr=
ession
>> I got from the docs but it wasn't totally clear to me.
>>
>> On Mon, Jun 27, 2011 at 3:33 PM, Jonathan Ellis <jbellis@gmail.com> wrot=
e:
>>>
>>> There's a JMX method to get the number of sstables in a CF, is that
>>> what you're looking for?
>>>
>>> On Mon, Jun 27, 2011 at 1:04 PM, Ethan Rowe <ethan@the-rowes.com> wrote=
:
>>> > Is there any straightforward means of seeing what's going on after
>>> > issuing a
>>> > truncate (on 0.7.5)? =A0I'm not seeing evidence that anything actuall=
y
>>> > happened. =A0I've disabled read repair on the column family in questi=
on
>>> > and
>>> > don't have anything actively reading/writing at present, apart from m=
y
>>> > one-off tests to see if rows have disappeared.
>>> > Thanks in advance.
>>>
>>>
>>>
>>> --
>>> Jonathan Ellis
>>> Project Chair, Apache Cassandra
>>> co-founder of DataStax, the source for professional Cassandra support
>>> http://www.datastax.com
>>
>>
>
>
>
> --
> Jonathan Ellis
> Project Chair, Apache Cassandra
> co-founder of DataStax, the source for professional Cassandra support
> http://www.datastax.com
>