Details
-
Improvement
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
Operability
-
Normal
-
All
-
Clients
-
Description
Right now, CAS uncertainty introduced in https://issues.apache.org/jira/browse/CASSANDRA-6013 is propagating as WriteTimeout. One of this conditions it manifests is when there’s at least one acceptor that has accepted the value, which means that this value may still get accepted during the later round, despite the proposer failure. Similar problem happens with CAS contention, which is also indistinguishable from the “regular” timeout, even though it is visible in metrics correctly.
Attachments
Attachments
Issue Links
- is duplicated by
-
CASSANDRA-9330 CAS timeout errors should use a different exception than WriteTimeoutException as WTE can happen when nodes fail to respond.
- Resolved
-
CASSANDRA-7822 Confusing timeout on CAS contention
- Resolved
- relates to
-
CASSANDRA-9328 WriteTimeoutException thrown when LWT concurrency > 1, despite the query duration taking MUCH less than cas_contention_timeout_in_ms
- Resolved
- links to