Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 380609961 for ; Sun, 4 Dec 2011 21:37:35 +0000 (UTC) Received: (qmail 56472 invoked by uid 500); 4 Dec 2011 21:37:33 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 56430 invoked by uid 500); 4 Dec 2011 21:37:33 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 56422 invoked by uid 99); 4 Dec 2011 21:37:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 Dec 2011 21:37:33 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [216.82.243.99] (HELO mail45.messagelabs.com) (216.82.243.99) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 Dec 2011 21:37:27 +0000 X-Env-Sender: Bryce.Godfrey@azaleos.com X-Msg-Ref: server-16.tower-45.messagelabs.com!1323034623!6440988!1 X-Originating-IP: [96.31.162.253] X-StarScan-Version: 6.4.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 404 invoked from network); 4 Dec 2011 21:37:04 -0000 Received: from unknown (HELO smtp.azaleos.net) (96.31.162.253) by server-16.tower-45.messagelabs.com with AES128-SHA encrypted SMTP; 4 Dec 2011 21:37:04 -0000 Received: from FISH-EX2K10-01.azaleos.net ([fe80::389b:5e08:38cd:b989]) by FISH-EX2K10-02.azaleos.net ([fe80::85f5:89cb:1aac:93ac%14]) with mapi id 14.01.0355.002; Sun, 4 Dec 2011 13:37:03 -0800 From: Bryce Godfrey To: "user@cassandra.apache.org" Subject: RE: Client Timeouts on incrementing counters Thread-Topic: Client Timeouts on incrementing counters Thread-Index: Acygc3RedNZV1GDSSNSxaIeXEvOFlAAdi9AAAIBmeQAD+Fnt4A== Date: Sun, 4 Dec 2011 21:37:02 +0000 Message-ID: <376CEC01195C894CB9F8A3C274029A96B460BF6A@FISH-EX2K10-01.azaleos.net> References: <2E7DE59E63E62E428DCDF9A173D43BF12560B75539@soco-ex02.ocom.lan> <2E7DE59E63E62E428DCDF9A173D43BF12560B7555A@soco-ex02.ocom.lan> In-Reply-To: <2E7DE59E63E62E428DCDF9A173D43BF12560B7555A@soco-ex02.ocom.lan> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.15.1.120] Content-Type: multipart/alternative; boundary="_000_376CEC01195C894CB9F8A3C274029A96B460BF6AFISHEX2K1001aza_" MIME-Version: 1.0 --_000_376CEC01195C894CB9F8A3C274029A96B460BF6AFISHEX2K1001aza_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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 jus= t constantly times out trying to increment them. No errors in the event lo= gs or any other issues with my cluster. Did you find a resolution? From: Carlos Rolo [mailto:c.rolo@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 no= des one-by-one. From: Tyler Hobbs [mailto:tyler@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 > wrote: Also Cassandra logs have lots (as in, several times per second) of this mes= sage 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 --_000_376CEC01195C894CB9F8A3C274029A96B460BF6AFISHEX2K1001aza_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I’m seeing this sam= e problem after upgrade to 1.0.3 from .8

 <= /p>

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

 <= /p>

Did you find a resolution= ?

 <= /p>

From: Carlos R= olo [mailto:c.rolo@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 informatio= n.

 <= /p>

It seems that all started= after I upgraded Cassandra from 0.8.x to 1.0.0

When I do a incr on the C= LI 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 ro= lling restart of all nodes one-by-one.

 <= /p>

 <= /p>

From: Tyler Ho= bbs [mailto:tyler@datastax.com]<= /a>
Sent: vrijdag 11 november 2011 20:18
To: user@cassandra.apac= he.org
Subject: Re: Client Timeouts on incrementing counters

 

On Fri, Nov 11, 2011 at 7:17 AM, C= arlos Rolo <c.rolo@ocom.com> w= rote:

Also Cassandra logs have lots (as in, several times per second) of= this message now:

 

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

 

What does the CLI say the row_cache_save_period_in_seconds for this CF is?<= br>
--
Tyler Hobbs
DataStax=

--_000_376CEC01195C894CB9F8A3C274029A96B460BF6AFISHEX2K1001aza_--