Re: All subsequent CAS requests time out after heavy use of new CAS feature

Oh yes it is, like Couters :-) On Sat, Dec 24, 2016 at 4:02 AM, Edward Capriolo wrote: > Anecdotal CAS works differently than the typical cassandra workload. If > you run a stress instance 3 nodes one host, you find that you typically run > into CPU issues, but if you

Re: All subsequent CAS requests time out after heavy use of new CAS feature

Anecdotal CAS works differently than the typical cassandra workload. If you run a stress instance 3 nodes one host, you find that you typically run into CPU issues, but if you are doing a CAS workload you see things timing out and before you hit 100% CPU. It is a strange beast. On Fri, Dec 23,

Re: All subsequent CAS requests time out after heavy use of new CAS feature

Update: I replace all quorum reads on that table with serial reads, and now these errors got less. Somehow quorum reads on CAS values cause most of these WTEs. Also I found two tickets on that topic: https://issues.apache.org/jira/browse/CASSANDRA-9328

Re: All subsequent CAS requests time out after heavy use of new CAS feature

Hi, I would like to warm up this old thread. I did some debugging and found out that the timeouts are coming from StorageProxy.proposePaxos() - callback.isFullyRefused() returns false and therefore triggers a WriteTimeout. Looking at my ccm cluster logs, I can see that two replica nodes return

Re: All subsequent CAS requests time out after heavy use of new CAS feature

My thinking was that due to the size of the data that there maybe I/O issues. But it sounds more like you're competing for locks and hit a deadlock issue. Regards, Denise Cell - (860)989-3431 Sent from mi iPhone > On Apr 15, 2016, at 9:00 AM, horschi wrote: > > Hi Denise,

Re: All subsequent CAS requests time out after heavy use of new CAS feature

Also, what type of data were you reading/writing? Regards, Denise Sent from mi iPad > On Apr 15, 2016, at 8:29 AM, horschi wrote: > > Hi Jan, > > were you able to resolve your Problem? > > We are trying the same and also see a lot of WriteTimeouts: >

Re: All subsequent CAS requests time out after heavy use of new CAS feature

Hi Jan, were you able to resolve your Problem? We are trying the same and also see a lot of WriteTimeouts: WriteTimeoutException: Cassandra timeout during write query at consistency SERIAL (2 replica were required but only 1 acknowledged the write) How many clients were competing for a lock in

Re: All subsequent CAS requests time out after heavy use of new CAS feature

On Mon, Sep 16, 2013 at 9:09 AM, Jan Algermissen jan.algermis...@nordsc.com wrote: I am experimenting with C* 2.0 ( and today's java-driver 2.0 snapshot) for implementing distributed locks. [ and I'm experiencing the problem described in the subject ... ] Any idea how to approach this