[
https://issues.apache.org/jira/browse/CASSANDRA-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882303#action_12882303
]
Sylvain Lebresne commented on CASSANDRA-1072:
---------------------------------------------
Not sure we can 'trust' HH since we can't be sure that they will be
delivered correctly (plus a node could not be hinted but still not get
the write if we don't wait for it and are unlucky).
But it's probably not too hard to change the writeResponseHandler
so that it at least wait for a specific node. And if we choose a live node
and the 'closest' one (either local or using the snitch), it's probably
fine.
Other than that, I must say that I find a bit sad that to be sure you
get the more up to date version of a count you have to use CL.ALL.
But truth is I don't see a way around it.
> Increment counters
> ------------------
>
> Key: CASSANDRA-1072
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1072
> Project: Cassandra
> Issue Type: Sub-task
> Components: Core
> Reporter: Johan Oskarsson
> Assignee: Kelvin Kakugawa
> Attachments: CASSANDRA-1072-2.patch, CASSANDRA-1072.patch
>
>
> Break out the increment counters out of CASSANDRA-580. Classes are shared
> between the two features but without the plain version vector code the
> changeset becomes smaller and more manageable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
