On Thu, May 23, 2013 at 1:58 PM, wrote:
>>>
>>>> Maybe you didn’t set the TTL correctly.
>>>>
>>>> Check the TTL of the column using CQL, e.g.:
>>>>
>>>> SELECT TTL (colName) from colFamilyName WHERE ;
>>>>
&g
gt;>
>>
>>
>> On Thu, May 23, 2013 at 1:58 PM, wrote:
>>
>>> Maybe you didn’t set the TTL correctly.
>>>
>>> Check the TTL of the column using CQL, e.g.:****
>>>
>>> SELECT TTL (colName) from colFamilyName WHERE ;
>>>
&g
et the TTL correctly.
>>
>> Check the TTL of the column using CQL, e.g.:
>>
>> SELECT TTL (colName) from colFamilyName WHERE ;
>>
>> ** **
>>
>> *From:* Felipe Sere [mailto:felipe.s...@1und1.de]
>> *Sent:* Thursday, May 23, 2013 1:28 PM
>
By "it is still there" I mean that when I do get request in Cassandra cli I
get the column, as well as when I try to read the column using Hector.
I don't think it is a matter of tombstone. I have the default
gc_grace_seconds and I run repair weekly (will run on Sunday).
Other columns for same CF e
On Wed, May 22, 2013 at 11:32 PM, Tamar Fraenkel wrote:
> I am using Hector HLockManagerImpl, which creates a keyspace named
> HLockManagerImpl and CF HLocks.
> For some reason I have a row with single column that should have expired
> yesterday who is still there.
> I tried deleting it using cli,
.@tok-media.com]
> *Sent:* Thursday, May 23, 2013 2:17 PM
> *To:* user@cassandra.apache.org
> *Subject:* Re: column with TTL of 10 seconds lives very long...
>
> ** **
>
> Hi!
>
> TTL was set:
>
> [default@HLockingManager] get
> HLocks['/LockedTopic/3
From: Tamar Fraenkel [mailto:ta...@tok-media.com]
Sent: Thursday, May 23, 2013 2:17 PM
To: user@cassandra.apache.org
Subject: Re: column with TTL of 10 seconds lives very long...
Hi!
TTL was set:
[default@HLockingManager] get
HLocks['/LockedTopic/31a30c12-652d-45b3-9ac2-0401cce85517
ld only live for about 5-10secs.
>
> Any ideas how to investigate this further from the Cassandra-side?
> --
>
> *Von:* Tamar Fraenkel [ta...@tok-media.com]
> *Gesendet:* Donnerstag, 23. Mai 2013 11:58
> *An:* user@cassandra.apache.org
> *
-side?
Von: Tamar Fraenkel [ta...@tok-media.com]
Gesendet: Donnerstag, 23. Mai 2013 11:58
An: user@cassandra.apache.org<mailto:user@cassandra.apache.org>
Betreff: Re: column with TTL of 10 seconds lives very long...
Thanks for the response.
Running date simult
?
Von: Tamar Fraenkel [ta...@tok-media.com]
Gesendet: Donnerstag, 23. Mai 2013 11:58
An: user@cassandra.apache.org
Betreff: Re: column with TTL of 10 seconds lives very long...
Thanks for the response.
Running date simultaneously on all nodes (using parallel ssh) shows that
Thanks for the response.
Running date simultaneously on all nodes (using parallel ssh) shows that
they are synced.
Tamar
*Tamar Fraenkel *
Senior Software Engineer, TOK Media
[image: Inline image 1]
ta...@tok-media.com
Tel: +972 2 6409736
Mob: +972 54 8356490
Fax: +972 2 5612956
On Thu,
Did you synchronized the clocks between servers?
On Thu, May 23, 2013 at 9:32 AM, Tamar Fraenkel wrote:
> Hi!
> I have Cassandra cluster with 3 node running version 1.0.11.
>
> I am using Hector HLockManagerImpl, which creates a keyspace named
> HLockManagerImpl and CF HLocks.
> For some reason
Hi!
I have Cassandra cluster with 3 node running version 1.0.11.
I am using Hector HLockManagerImpl, which creates a keyspace named
HLockManagerImpl and CF HLocks.
For some reason I have a row with single column that should have expired
yesterday who is still there.
I tried deleting it using cli,
13 matches
Mail list logo
