You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2014/02/03 23:03:06 UTC
[jira] [Comment Edited] (CASSANDRA-6510) Don't drop local mutations
without a hint
[ https://issues.apache.org/jira/browse/CASSANDRA-6510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889949#comment-13889949 ]
Jonathan Ellis edited comment on CASSANDRA-6510 at 2/3/14 10:01 PM:
--------------------------------------------------------------------
Nope, that's not the implication. You can see from the code that {{responseHandler.response}} only gets called after {{rm.apply}}. That is, no write is acknowledged if it hasn't actually been applied.
was (Author: jbellis):
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 hint
> -----------------------------------------
>
> 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 hint. SP.insertLocal() should be using LocalMutationRunnable instead.
> Note: hints are the context here, not consistency.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)