You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Yuki Morishita (JIRA)" <ji...@apache.org> on 2012/11/06 00:30:12 UTC

[jira] [Commented] (CASSANDRA-4906) Avoid flushing other columnfamilies on truncate

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

Yuki Morishita commented on CASSANDRA-4906:
-------------------------------------------

I'm seeing truncated data appear again after commit log replay.
Looks like we have to flush system.local after truncate, otherwise we are not able to query 'truncated_at' properly before commit log replays update of truncated_at.
                
> Avoid flushing other columnfamilies on truncate
> -----------------------------------------------
>
>                 Key: CASSANDRA-4906
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4906
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Minor
>             Fix For: 1.2.0
>
>         Attachments: 4906.txt
>
>
> Currently truncate flushes *all* columnfamilies so it can get rid of the commitlog segments containing truncated data.  Otherwise, it could be replayed on restart since the replay position is contained in the sstables we're trying to delete.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira