You need to create the tombstone in case the data was inserted without a
timestamp at some point.
-Jeremiah
From: Radim Kolar [h...@filez.com]
Sent: Monday, March 19, 2012 4:48 PM
To: user@cassandra.apache.org
Subject: Re: repair broke TTL based
I suspect that running cluster wide repair interferes with TTL based
expiration. I am running repair every 7 days and using TTL expiration
time 7 days too. Data are never deleted.
Stored data in cassandra are always growing (watching them for 3 months)
but they should not. If i run manual
Hello
Datasize should decrease during minor compactions. Check logs for compactions
results.
-Original Message-
From: Radim Kolar h...@filez.com
To: user@cassandra.apache.org
Sent: Mon, 19 Mar 2012 12:16
Subject: repair broke TTL based expiration
I suspect that running cluster
Dne 19.3.2012 20:28, i...@4friends.od.ua napsal(a):
Hello
Datasize should decrease during minor compactions. Check logs for
compactions results.
they do but not as much as i expect. Look at sizes and file dates:
-rw-r--r-- 1 root wheel 5.4G Feb 23 17:03 resultcache-hc-27045-Data.db
Dne 19.3.2012 21:46, Caleb Rackliffe napsal(a):
I've been wondering about this too, but every column has both a
timestamp /and/ a TTL. Unless the timestamp is not preserved, there
should be no need to adjust the TTL, assuming the expiration time is
determined from these two variables.
Do you make major compaction??
2012/3/19 Radim Kolar h...@filez.com:
I suspect that running cluster wide repair interferes with TTL based
expiration. I am running repair every 7 days and using TTL expiration time 7
days too. Data are never deleted.
Stored data in cassandra are always growing
Dne 19.3.2012 23:33, ruslan usifov napsal(a):
Do you make major compaction??
no, i do cleanups only. Major compactions kills my node with OOM.
.
-Original Message-
From: Radim Kolar h...@filez.com
To: user@cassandra.apache.org
Sent: Mon, 19 Mar 2012 23:48
Subject: Re: repair broke TTL based expiration
Dne 19.3.2012 20:28, i...@4friends.od.ua napsal(a):
Hello
Datasize should decrease during minor compactions. Check logs for
compactions
cleanup in you case doesn't have any seens. You write that repair work
for you, so you can stop cassandra daemon, delete all data from folder
that contain problem data, start cassandra daemon, and run nodetool
repair, but in this case ypu must have replication factor for keyspace
3 and have
