You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "C. Scott Andreas (JIRA)" <ji...@apache.org> on 2018/11/18 17:52:01 UTC
[jira] [Updated] (CASSANDRA-12625) Distinguish between CAS prepare
and propose failures
[ https://issues.apache.org/jira/browse/CASSANDRA-12625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
C. Scott Andreas updated CASSANDRA-12625:
-----------------------------------------
Component/s: Coordination
> Distinguish between CAS prepare and propose failures
> ----------------------------------------------------
>
> Key: CASSANDRA-12625
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12625
> Project: Cassandra
> Issue Type: Improvement
> Components: Coordination
> Reporter: Christopher Batey
> Assignee: Christopher Batey
> Priority: Minor
> Labels: LWT, cas
> Fix For: 4.x
>
>
> I spoke to a lot of users at the summit and had the feedback that the hardest part of building applications using LWTs is dealing with WriteTimeouts of type CAS.
> Following up from https://issues.apache.org/jira/browse/CASSANDRA-8672 I think we should add a separate WriteType for timing out during the prepare phase assuming we can advise users to retry the operation or be confident it has failed as it won't be completed by a later SERIAL read or LWT.
> We can't remove the ambiguity at the propose phase but this will remove one of the unknown cases.
> cc [~slebresne] [~bdeggleston] [~spodxx@gmail.com]
> Happy to do a patch for this but assuming it will need a native protocol change when can we do it?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org