Re: error in cassandra log file under stress

2014-05-06 Thread Mohica Jasha
Thanks Robert, I understand that C* < 2.1 is probably not perfect for prod. But the choice to use C* 2.0.x was made long ago and we are trying to keep up. Anyway I filled a jira ticket: https://issues.apache.org/jira/browse/CASSANDRA-7176 On Mon, May 5, 2014 at 5:51 PM, Robert Coli wrote: >

Re: error in cassandra log file under stress

2014-05-05 Thread Robert Coli
On Mon, May 5, 2014 at 2:03 PM, Mohica Jasha wrote: > Our prod deployment: > > C* 2.0.5, DC1:3, DC2:3 > Not directly related to your bug report, which I would file an Apache JIRA regarding, but... https://engineering.eventbrite.com/what-version-of-cassandra-should-i-run/ =Rob

Re: error in cassandra log file under stress

2014-05-05 Thread Mohica Jasha
Most likely it is the following query: DELETE from conditional_update_lock where resource_id = '${myresourceid}' IF lock_id = ${myuuid}; We are using datastax 2.0.1 and the datastax threw a ReadtimeoutException On Mon, May 5, 2014 at 5:03 PM, Mohica Jasha wrote: > forgot to say which Cassa

Re: error in cassandra log file under stress

2014-05-05 Thread Mohica Jasha
forgot to say which Cassandra version we are using. Our prod deployment: C* 2.0.5, DC1:3, DC2:3 On Mon, May 5, 2014 at 5:01 PM, Mohica Jasha wrote: > one query in our prod system under heavy load failed. > I cant tell which query it was. But I don't think we were using an invalid > consiste

error in cassandra log file under stress

2014-05-05 Thread Mohica Jasha
one query in our prod system under heavy load failed. I cant tell which query it was. But I don't think we were using an invalid consistency level since our configuration work all the time except when it goes under heavy load. If I can reproduce this I will pass more information. I wonder if this