Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Sun, 24 Aug 2014 01:14:11 +0000 (UTC)
From: "sankalp kohli (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12736295.1408842836938.21129.1408842851737@arcas>
In-Reply-To: <JIRA.12736295.1408842836938@arcas>
References: <JIRA.12736295.1408842836938@arcas>
Subject: [jira] [Created] (CASSANDRA-7822) Confusing timeout on CAS
 contention
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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)