You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2013/09/09 15:21:52 UTC
[jira] [Commented] (CASSANDRA-5985) Paxos replay of in progress
update is incorrect
[ https://issues.apache.org/jira/browse/CASSANDRA-5985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13761827#comment-13761827 ]
Sylvain Lebresne commented on CASSANDRA-5985:
---------------------------------------------
One "nit": I'm not sure sleeping in the case where the propose work (and we commit) is really useful, the commit itself probably play a good enough sleep if we're contending (which, for what its worth, is confirmed by my unscientific test: moving the sleep only if the propose fails perform slightly better without making threads retry more often).
But overall, +1 on the fix (a quick test (that I'll commit to dtests) does confirm the current CAS timeout as soon a 2 inserts contend a bit too much).
> Paxos replay of in progress update is incorrect
> -----------------------------------------------
>
> Key: CASSANDRA-5985
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5985
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Sylvain Lebresne
> Fix For: 2.0.1
>
>
> When we replay {{inProgress}}, we need to refresh it with the newly prepared ballot, or it will be (correctly) rejected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira