[jira] [Comment Edited] (CASSANDRA-4667) optimize memtable deletions for batchlog

["Jonathan Ellis (JIRA)" <ji...@apache.org>]

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

Jonathan Ellis edited comment on CASSANDRA-4667 at 10/3/12 4:52 AM:
--------------------------------------------------------------------

v3 LGTM.  Still might want to add flush/compact after replay logic from v2 tho.
                
      was (Author: jbellis):
    v2 LGTM.  Still might want to add flush/compact after replay logic from v2 tho.
                  
> optimize memtable deletions for batchlog
> ----------------------------------------
>
>                 Key: CASSANDRA-4667
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4667
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Aleksey Yeschenko
>            Assignee: Aleksey Yeschenko
>         Attachments: CASSANDRA-4667-v1.1.patch, CASSANDRA-4667-v2.patch, CASSANDRA-4667-v3.txt
>
>
> Batchlog writes with the same key are never retried. This means that if a batchlog row is in the memtable, it can't be in any of the sstables, ever. In such cases we don't need to write a tombstone to disk. We can purge the row completely from the memtable and only write a tombstone if the row had been flushed already (if it's not in the memtable then it must be in one of the sstables).

--
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