[ 
https://issues.apache.org/jira/browse/CASSANDRA-6801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13922246#comment-13922246
 ] 

Sylvain Lebresne commented on CASSANDRA-6801:
---------------------------------------------

bq. Then add some data and flush it to ensure the sstables exist (didn't 
reproduce in memtables for some reason).

More detail on those steps would help because currently I'm not able to 
reproduce this. Truly, a dtest (something along the lines of 
https://github.com/riptano/cassandra-dtest/blob/master/cql_tests.py#L3778 for 
instance) would really be perfect, but short of that, it would be nice to 
reduce the repro steps to the minimum that still allow to reproduce. For 
instance, why 2 DCs with 3 nodes each? Are you not able to reproduce with a 
single node (which, because it would be extremely surprising would be an 
important information to have)? Also, have you made sure that you wait enough 
before testing the 2nd insert (typically, waiting 5 seconds would make it 
likely for the insert to fail, but for a following select to return nothing)? 
Ideally, testing against the current 2.0 branch would be nice just to make sure 
CASSANDRA-6623 didn't solve that either (though I did try to reproduce against 
2.0.5 with no luck so I'm not saying that's the case).

> INSERT with IF NOT EXISTS fails when row is an expired ttl
> ----------------------------------------------------------
>
>                 Key: CASSANDRA-6801
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6801
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Adam Hattrell
>
> I ran this on a 2 DC cluster with 3 nodes each.  
> CREATE KEYSPACE test WITH replication = {
> 'class': 'NetworkTopologyStrategy',
> 'DC1': '3',
> 'DC2': '3'
> };
> CREATE TABLE clusterlock (
> name text,
> hostname text,
> lockid text,
> PRIMARY KEY (name)
> ) ;
> Then add some data and flush it to ensure the sstables exist (didn't 
> reproduce in memtables for some reason).
> Then
>  insert into clusterlock (name, lockid, hostname) values  ( 'adam', 'tt', 
> '111') IF NOT EXISTS USING TTL 5;
> Wait for ttl to be reached then try again:
>  insert into clusterlock (name, lockid, hostname) values  ( 'adam', 'tt', 
> '111') IF NOT EXISTS USING TTL 5;
>  
> [applied]
> -----------
>      False
> select * shows no rows in table.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to