I use truncate between my test cases. Never had a problem with one test
case inheriting the data from the previous one. I¹m using a single node,
so that may be why.
On 2/26/14, 9:27 AM, "Ben Hood" <0x6e6...@gmail.com> wrote:
>On Wed, Feb 26, 2014 at 3:58 PM, DuyHai Doan wrote:
>> Try truncate fo
On Wed, Feb 26, 2014 at 3:59 PM, Tupshin Harper wrote:
> This is a known issue that is fixed in 2.1beta1.
> https://issues.apache.org/jira/browse/CASSANDRA-5202
>
> Until 2.1, we do not recommend relying on the recycling of tables through
> drop/create or truncate.
>
> However, on a single node cl
On Wed, Feb 26, 2014 at 3:58 PM, DuyHai Doan wrote:
> Try truncate foo instead of drop table foo.
>
> About the nodetool clearsnapshot, I've experienced the same behavior also
> before. Snapshots cleaning is not immediate
I get the same behavior with truncate as well.
I've played with it using a 2 nodes cluster with auto_snapshot = false in
cassandra.yaml and by deactivating durable write (no commitlog). In my
case, truncating tables allows cleaning up data.
With "nodetool status", I can see the data payload decreasing from Gb to
some kbytes
On Wed, Feb 26,
This is a known issue that is fixed in 2.1beta1.
https://issues.apache.org/jira/browse/CASSANDRA-5202
Until 2.1, we do not recommend relying on the recycling of tables through
drop/create or truncate.
However, on a single node cluster, I suspect that truncate will work far
more reliably than drop
Try truncate foo instead of drop table foo.
About the nodetool clearsnapshot, I've experienced the same behavior also
before. Snapshots cleaning is not immediate
On Wed, Feb 26, 2014 at 4:53 PM, Ben Hood <0x6e6...@gmail.com> wrote:
> On Wed, Feb 26, 2014 at 3:17 PM, DuyHai Doan wrote:
> > "I'm
On Wed, Feb 26, 2014 at 3:17 PM, DuyHai Doan wrote:
> "I'm noticing that using either TRUNCATE or DROP/CREATE in cqlsh appear to
> leave the underlying data behind."
>
> --> What do you mean by "underlying data" ? Are you talking about
> "snapshots" ?
I was referring to all of the state related
"I'm noticing that using either TRUNCATE or DROP/CREATE in cqlsh appear to
leave the underlying data behind."
--> What do you mean by "underlying data" ? Are you talking about
"snapshots" ?
If yes, you can wipe them using nodetool clearsnapshots command
On Wed, Feb 26, 2014 at 4:14 PM, Ben Ho
Hi,
I'm trying to truncate data on a single node 2.0.5 instance and I'm
noticing that using either TRUNCATE or DROP/CREATE in cqlsh appear to
leave the underlying data behind.
So I was wondering what nodetool operation I should use to completely
nuke the old data, short of dropping the entire key
