cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4667) optimize memtable deletions for batchlog
Date Fri, 05 Oct 2012 22:48:03 GMT

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

Aleksey Yeschenko commented on CASSANDRA-4667:
----------------------------------------------

The patch works. +1
                
> 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
>             Fix For: 1.2.0 beta 2
>
>         Attachments: 4667-handle-empty-flushes.txt, CASSANDRA-4667-v1.1.patch, CASSANDRA-4667-v2.patch,
CASSANDRA-4667-v3.txt, CASSANDRA-4667-v4.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

Mime
View raw message