Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 3 Feb 2014 21:41:06 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12685590.1387460017311.29628.1391463666806@arcas>
In-Reply-To: <JIRA.12685590.1387460017311@arcas>
References: <JIRA.12685590.1387460017311@arcas>
Subject: [jira] [Commented] (CASSANDRA-6510) Don't drop local mutations
 without a trace
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis commented on CASSANDRA-6510:
-------------------------------------------

Nope, that's not the implication.  You can easily see from the code that {{responseHandler.response}} only gets called after {{rm.apply}}.  That is, no write is acknowledge if it hasn't actually been applied.

> Don't drop local mutations without a trace
> ------------------------------------------
>
>                 Key: CASSANDRA-6510
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6510
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Aleksey Yeschenko
>            Assignee: Aleksey Yeschenko
>             Fix For: 1.2.14, 2.0.4
>
>         Attachments: 6510.txt
>
>
> SP.insertLocal() uses a regular DroppableRunnable, thus timed out local mutations get dropped without leaving a trace. SP.insertLocal() should be using LocalMutationRunnable instead.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)