Christopher Batey created CASSANDRA-12625:
---------------------------------------------
Summary: Distinguish between CAS prepare and propose failures
Key: CASSANDRA-12625
URL: https://issues.apache.org/jira/browse/CASSANDRA-12625
Project: Cassandra
Issue Type: Improvement
Reporter: Christopher Batey
Assignee: Christopher Batey
Priority: Minor
Fix For: 3.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] [[email protected]]
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
(v6.3.4#6332)
