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

Posted to commits@cassandra.apache.org by "Stefania (JIRA)" <ji...@apache.org> on 2016/01/04 17:42:39 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=15081334#comment-15081334 ] 

Stefania commented on CASSANDRA-9949:
-------------------------------------

[~iamaleksey] : can you confirm this is required on all versions, including 2.1?

Is looking at memtables when calculating the max purgeable timestamp all that's required (along with swapping the predicate and tests)? See [here|https://github.com/stef1927/cassandra/commit/e5be5cfafcfd203e1267367d94ae38c03d9d3793] for 2.1.

> maxPurgeableTimestamp needs to check memtables too
> --------------------------------------------------
>
>                 Key: CASSANDRA-9949
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9949
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Local Write-Read Paths
>            Reporter: Jonathan Ellis
>            Assignee: Stefania
>             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)