cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sankalp kohli (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-7822) Confusing timeout on CAS contention
Date Sun, 24 Aug 2014 01:14:11 GMT
sankalp kohli created CASSANDRA-7822:
----------------------------------------

             Summary: Confusing timeout on CAS contention
                 Key: CASSANDRA-7822
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7822
             Project: Cassandra
          Issue Type: Improvement
            Reporter: sankalp kohli
            Priority: Minor


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
(v6.2#6252)

Mime
View raw message