Re: column expiration and rows in 0.7

2010-09-23 Thread Sylvain Lebresne
l Message- >> From: "Aaron Morton" >> Sent: Wednesday, September 22, 2010 7:47pm >> To: "user@cassandra.apache.org" >> Subject: Re: column expiration and rows in 0.7 >> >> The data will only be physically deleted when a major compaction runs and >&

Re: column expiration and rows in 0.7

2010-09-23 Thread Alaa Zubaidi
rowse/CASSANDRA-1074 -Original Message- From: "Aaron Morton" Sent: Wednesday, September 22, 2010 7:47pm To: "user@cassandra.apache.org" Subject: Re: column expiration and rows in 0.7 The data will only be physically deleted when a major compaction runs and the GCGraceSec

Re: column expiration and rows in 0.7

2010-09-22 Thread Stu Hood
010 7:47pm To: "user@cassandra.apache.org" Subject: Re: column expiration and rows in 0.7 The data will only be physically deleted when a major compaction runs and the GCGraceSeconds has passed. You need to trigger the compaction using node tool. http://wiki.apache.org/cassandra/Distr

Re: column expiration and rows in 0.7

2010-09-22 Thread Aaron Morton
The data will only be physically deleted when a major compaction runs and the GCGraceSeconds has passed. You need to trigger the compaction using node tool. http://wiki.apache.org/cassandra/DistributedDeletes Aaron On 23 Sep 2010, at 12:14, Alaa Zubaidi wrote: > Hi, > I am expecting my data s

column expiration and rows in 0.7

2010-09-22 Thread Alaa Zubaidi
Hi, I am expecting my data size to be around nGB. However, it keeps growing and growing. I am setting the gc_grace_seconds for the CF to 5 hours, and I am also setting "ttl" for all columns on a row and expecting that these columns will be "deleted" after the ttl time, and will be "removed"