RE: Client Timeouts on incrementing counters

[Bryce Godfrey]

I'm seeing this same problem after upgrade to 1.0.3 from .8

Nothing changed with the column family storing the counters, but now it just 
constantly times out trying to increment them.  No errors in the event logs or 
any other issues with my cluster.

Did you find a resolution?

From: Carlos Rolo [mailto:c.r...@ocom.com]
Sent: Monday, November 14, 2011 12:34 AM
To: user@cassandra.apache.org
Subject: RE: Client Timeouts on incrementing counters

I have digged a bit more to try to find the root cause of the error, and I have 
some more information.

It seems that all started after I upgraded Cassandra from 0.8.x to 1.0.0
When I do a incr on the CLI I also get a timeout.
row_cache_save_period_in_seconds is set to 60sec.

Could be a problem from the upgrade? I just did a rolling restart of all nodes 
one-by-one.


From: Tyler Hobbs 
[mailto:ty...@datastax.com]<mailto:[mailto:ty...@datastax.com]>
Sent: vrijdag 11 november 2011 20:18
To: user@cassandra.apache.org<mailto:user@cassandra.apache.org>
Subject: Re: Client Timeouts on incrementing counters

On Fri, Nov 11, 2011 at 7:17 AM, Carlos Rolo 
mailto:c.r...@ocom.com>> wrote:
Also Cassandra logs have lots (as in, several times per second) of this message 
now:

INFO 14:15:25,740 Saved ClusterCassandra-CounterFamily-RowCache (52 items) in 1 
ms


What does the CLI say the row_cache_save_period_in_seconds for this CF is?

--
Tyler Hobbs
DataStax<http://datastax.com/>

RE: Client Timeouts on incrementing counters

[Carlos Rolo]

I have digged a bit more to try to find the root cause of the error, and I have 
some more information.

It seems that all started after I upgraded Cassandra from 0.8.x to 1.0.0
When I do a incr on the CLI I also get a timeout.
row_cache_save_period_in_seconds is set to 60sec.

Could be a problem from the upgrade? I just did a rolling restart of all nodes 
one-by-one.


From: Tyler Hobbs [mailto:ty...@datastax.com]
Sent: vrijdag 11 november 2011 20:18
To: user@cassandra.apache.org
Subject: Re: Client Timeouts on incrementing counters

On Fri, Nov 11, 2011 at 7:17 AM, Carlos Rolo 
mailto:c.r...@ocom.com>> wrote:
Also Cassandra logs have lots (as in, several times per second) of this message 
now:

INFO 14:15:25,740 Saved ClusterCassandra-CounterFamily-RowCache (52 items) in 1 
ms


What does the CLI say the row_cache_save_period_in_seconds for this CF is?

--
Tyler Hobbs
DataStax<http://datastax.com/>

Re: Client Timeouts on incrementing counters

[Tyler Hobbs]

On Fri, Nov 11, 2011 at 7:17 AM, Carlos Rolo  wrote:

> Also Cassandra logs have lots (as in, several times per second) of this
> message now:
>
> ** **
>
> INFO 14:15:25,740 Saved ClusterCassandra-CounterFamily-RowCache (52 items)
> in 1 ms 
>
>
>

What does the CLI say the row_cache_save_period_in_seconds for this CF is?

-- 
Tyler Hobbs
DataStax 

Client Timeouts on incrementing counters

[Carlos Rolo]

Hi,

I was having lots of problems with cassandra 0.8.x running OOM. After moving to 
Cassandra 1.0.x OOM just disappeared, but now, my python client is having 
troubles incrementing counters.

2/3 of the times it tries to increment a counter it get a Timeout exception. 
Also incrementing on CLI I get a Null response! I didn't had this problem with 
0.8.x.
Also Cassandra logs have lots (as in, several times per second) of this message 
now:

INFO 14:15:25,740 Saved ClusterCassandra-CounterFamily-RowCache (52 items) in 1 
ms


Replacing and adding new columns/rows is functioning perfectly.
I'm bagging my head against the wall checking where can I tune Cassandra to get 
rid of this error!

Thx,

Carlos Rolo