[jira] [Updated] (CASSANDRA-7822) Confusing timeout on CAS contention

["Benjamin Lerer (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-7822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Lerer updated CASSANDRA-7822:
--------------------------------------
    Resolution: Duplicate
        Status: Resolved  (was: Open)

> Confusing timeout on CAS contention
> -----------------------------------
>
>                 Key: CASSANDRA-7822
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7822
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Feature/Lightweight Transactions, Legacy/Coordination
>            Reporter: Sankalp Kohli
>            Priority: Low
>              Labels: LWT
>
> If we have contention in CAS and we hit the cas contention timeout, we throw an exception. In this timeout exception, we pass that 0 replicas responded. This is very confusing to someone looking at the client logs. I think we might need to throw a separate exception for contention or may be add a flag in the timeout exception. 
> We have seen many people confused by this so I think we should fix it. 
> This is how we throw it on contention. 
> throw new WriteTimeoutException(WriteType.CAS, consistencyForPaxos, 0, consistencyForPaxos.blockFor(Keyspace.open(keyspaceName)));



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org