[CASSANDRA-12625] Distinguish between CAS prepare and propose failures

• Type: Improvement
• Status: Open
• Priority: Low
• Resolution: Unresolved
• Fix Version/s: 5.x
• Component/s: Feature/Lightweight Transactions, Legacy/Coordination
• Labels: LWT cas
• Assignee: Christopher Batey
• Reporter: Christopher Batey

Authors

Christopher Batey

• Created: 10/Sep/16 15:15
• Updated: 07/Mar/23 10:54

Description

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 [e-mail]

Happy to do a patch for this but assuming it will need a native protocol change when can we do it?