cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9949) maxPurgeableTimestamp needs to check memtables too
Date Fri, 22 Jan 2016 09:11:40 GMT

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

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

The 3.0 patch is ready as well. This patch is much simpler than the 2.2 version because each
partition already has the minimum timestamp in {{stats().minTimestamp}}. There is a small
conflict from 3.0 to 3.3 (very easy to resolve) and then it merges clearly from 3.3 to trunk.

I'm still monitoring CI and I will move the ticket to patch available once CI is confirmed
fine.

||3.0||3.3||trunk||
|[patch|https://github.com/stef1927/cassandra/commits/9949-3.0]|[patch|https://github.com/stef1927/cassandra/commits/9949-3.3]|-|
|[testall|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-9949-3.0-testall/]|[testall|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-9949-3.3-testall/]|[testall|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-9949-testall/]|
|[dtest|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-9949-3.0-dtest/]|[dtest|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-9949-3.3-dtest/]|[dtest|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-9949-dtest/]|

> 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.2.x, 3.0.x, 3.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)

Mime
View raw message