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

Jonathan Ellis commented on CASSANDRA-2950:
-------------------------------------------

but we record CL "context" at time of flush in the sstable it makes, and we on 
replay we ignore any mutations from before that position.

checked and we do wait for flush to complete in truncate.

> Data from truncated CF reappears after server restart
> -----------------------------------------------------
>
>                 Key: CASSANDRA-2950
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2950
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Cathy Daw
>            Assignee: Brandon Williams
>
> * Configure 3 node cluster
> * Ensure the java stress tool creates Keyspace1 with RF=3
> {code}
> // Run Stress Tool to generate 10 keys, 1 column
> stress --operation=INSERT -t 2 --num-keys=50 --columns=20 
> --consistency-level=QUORUM --average-size-values --replication-factor=3 
> --create-index=KEYS --nodes=cathy1,cathy2
> // Verify 50 keys in CLI
> use Keyspace1; 
> list Standard1; 
> // TRUNCATE CF in CLI
> use Keyspace1;
> truncate counter1;
> list counter1;
> // Run stress tool and verify creation of 1 key with 10 columns
> stress --operation=INSERT -t 2 --num-keys=1 --columns=10 
> --consistency-level=QUORUM --average-size-values --replication-factor=3 
> --create-index=KEYS --nodes=cathy1,cathy2
> // Verify 1 key in CLI
> use Keyspace1; 
> list Standard1; 
> // Restart all three nodes
> // You will see 51 keys in CLI
> use Keyspace1; 
> list Standard1; 
> {code}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to