[jira] [Commented] (CASSANDRA-6427) Counter writes shouldn't be resubmitted after timeouts

["Jonathan Ellis (JIRA)" <ji...@apache.org>]

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

Jonathan Ellis commented on CASSANDRA-6427:
-------------------------------------------

But if it's dropped-then-resubmitted then the user would only retry if the resubmit times out, right?  So we're better off than we would be in at least some situations (dropped, resubmitted, not retried) and no worse off in others (succeeded after timeout, but retried).

> Counter writes shouldn't be resubmitted after timeouts
> ------------------------------------------------------
>
>                 Key: CASSANDRA-6427
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6427
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Aleksey Yeschenko
>            Assignee: Aleksey Yeschenko
>             Fix For: 1.2.13, 2.0.4
>
>         Attachments: 6427.txt
>
>
> CASSANDRA-4753 made SP.counterWriteTask() return a LocalMutationRunnable instead of the usual DroppableRunnalbe, and LMR resubmits the original runnable in case of timing out instead of simply dropping it.
> For counters this is not the right option since it would lead to overcounting if the mutation got dropped-then-resubmitted and then retried by the user.



--
This message was sent by Atlassian JIRA
(v6.1#6144)