Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 31 Jul 2015 22:59:04 +0000 (UTC)
From: "Aleksey Yeschenko (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12850710.1438381232000.344859.1438383544685@Atlassian.JIRA>
In-Reply-To: <JIRA.12850710.1438381232000@Atlassian.JIRA>
References: <JIRA.12850710.1438381232000@Atlassian.JIRA>
 <JIRA.12850710.1438381232646@arcas>
Subject: [jira] [Commented] (CASSANDRA-9949) maxPurgeableTimestamp needs to
 check memtables too
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Aleksey Yeschenko commented on CASSANDRA-9949:
----------------------------------------------

Very out of order, or just with ridiculously low gc gs.

This issue was raised by [~benedict] during CASSANDRA-6230 review, originally.

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