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 Wed, 13 Jan 2016 13:40:40 GMT

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

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

There is something really weird with the [first dtest run|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-9949-2.2-dtest/lastSuccessfulBuild/]:
all tests are failing with {{ERROR: Cassandra 3.0+ requires Java >= 1.8, found Java 1.7}}
but this is a 2.2 branch as confirmed by the version in _build.xml_. cc [~philipthompson]

Relaunched. 

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

Mime
View raw message