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

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2015/08/01 00:23:04 UTC

[jira] [Commented] (CASSANDRA-9949) maxPurgeableTimestamp needs to check memtables too

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

Jonathan Ellis commented on CASSANDRA-9949:
-------------------------------------------

Nit: should probably reverse the order of the predicates in {{timestamp < getMaxPurgeableTimestamp() && localDeletionTime < gcBefore}} since the former is expensive while the latter is not.

> maxPurgeableTimestamp needs to check memtables too
> --------------------------------------------------
>
>                 Key: CASSANDRA-9949
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9949
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Jonathan Ellis
>             Fix For: 2.1.x, 2.2.x
>
>
> overlapIterator/maxPurgeableTimestamp don't include the memtables, so a very-out-of-order write could be ignored



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)