C. Scott Andreas updated CASSANDRA-7822:
    Component/s: Coordination

> Confusing timeout on CAS contention
> -----------------------------------
>                 Key: CASSANDRA-7822
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7822
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Coordination
>            Reporter: sankalp kohli
>            Priority: Minor
>              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

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

Reply via email to