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 36A8ED8AA for ; Mon, 19 Nov 2012 08:58:11 +0000 (UTC) Received: (qmail 88752 invoked by uid 500); 19 Nov 2012 08:58:08 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 88728 invoked by uid 500); 19 Nov 2012 08:58:08 -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 88708 invoked by uid 99); 19 Nov 2012 08:58:07 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Nov 2012 08:58:07 +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: domain of arodrime@gmail.com designates 209.85.220.172 as permitted sender) Received: from [209.85.220.172] (HELO mail-vc0-f172.google.com) (209.85.220.172) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Nov 2012 08:58:01 +0000 Received: by mail-vc0-f172.google.com with SMTP id fw7so2564223vcb.31 for ; Mon, 19 Nov 2012 00:57:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=PWWqqHLxdrwYqV6IISILzGbCa+fQGV/YT4ym1bz69Qw=; b=grw84+1Tx5rNWB7YBEQpzCb/6z9R4gqRnaUBndBMPmCAifQbKdVBpodO/For1qz7GL hS1m6p1/7W+t4qe4ztyg4OVIZ60txsH8c+FVB+NdAp0dHFdOdgqrccNOuXkjtWUtpDRy X4UA1E4KF3PZzOzGeC7u/+asoTXmn2NGXwc2Tit0zHp72Qay1ZQgv9PitY1TX8/zytsL mjQfJvR5AL2sYPDbtQD9JQH/6sOtAmyCs4kM2c9etCPt8IbAoo4nXv1bItbk2JDOFubJ cpKrJk+sXtpDZJYe7/8iVDSm629juN2D7TGz/GtoGMKVnlqoupyipWlHdRS5rIwYR2GT MI1g== Received: by 10.220.148.134 with SMTP id p6mr17857010vcv.3.1353315460552; Mon, 19 Nov 2012 00:57:40 -0800 (PST) MIME-Version: 1.0 Received: by 10.220.249.3 with HTTP; Mon, 19 Nov 2012 00:57:20 -0800 (PST) In-Reply-To: <41F43370-8B1D-4A42-8673-C540E47FE7BB@thelastpickle.com> References: <78EE60A6-3864-4F93-B7F8-BB481A121D41@thelastpickle.com> <41F43370-8B1D-4A42-8673-C540E47FE7BB@thelastpickle.com> From: Alain RODRIGUEZ Date: Mon, 19 Nov 2012 09:57:20 +0100 Message-ID: Subject: Re: Upgrade 1.1.2 -> 1.1.6 To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=f46d043be1d44b96d204ced54f0d X-Virus-Checked: Checked by ClamAV on apache.org --f46d043be1d44b96d204ced54f0d Content-Type: text/plain; charset=ISO-8859-1 "This looks like the counters were more out of sync before the upgrade than after?" My guess is the update makes some counters over-count since I saw the value of the sum of our daily counter increase by 2000 after each restart at the exact moment that the node is marked as being up. This counter was about 5000, after upgrading the first node 7000, after the second upgrade 9000 and finally 11000. This value shouldn't have increase since we had stopped our storm topology and we were queuing events without writing directly into C*. "Do you know if your client is retrying counter operations ? (I saw some dropped messages in the S1 log). " I am using phpCassa written by Tyler Hobbs. I have a pool configured like this: $max_retries = 4 $send_timeout = 2000 $recv_timeout = 2000 $pool_size = NULL //max(5, count($servers) * 2) $pool = new ConnectionPool($base, $servers, $pool_size, $max_retries, $send_timeout, $recv_timeout); So I guess my client is retrying count operations like any other operation, 4 times max with 2 sec time out. "S1 shows a lot of Commit Log replay going on. Reading your timeline below this sounds like the auto restart catching you out." Is there a way to remove this auto-restart while upgrading from the Datastax repository on Ubuntu ? Let me know if you need something more to understand what happened. Alain --f46d043be1d44b96d204ced54f0d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable "This look= s like the counters were more out of sync before the upgrade than after?&qu= ot;

My guess is the update m= akes some counters over-count since I saw the value of the sum of our daily= counter increase by 2000 after each restart at the exact moment that the n= ode is marked as being up. This counter was about 5000, after upgrading the= first node 7000, after the second upgrade 9000 and finally 11000. This val= ue shouldn't have increase since we had stopped our storm topology and = we were=A0queuing=A0events without=A0writing directly into C*.

"Do you know if your client is retrying counter operations ?= (I saw some dropped messages in the S1 log). "

I am using phpCassa written by=A0Tyler Hobbs. I have a po= ol configured like this:
=
$max_retries= =3D 4
$send_timeout =3D 2000
$recv_timeou= t =3D 2000
$pool_size =3D=A0NULL =A0 =A0 //max(5, count($servers) *= 2)

<= /div>
$pool =3D new Connec= tionPool($base, $servers, $pool_size, $max_retries, $send_timeout, $recv_ti= meout);

So I guess my client is ret= rying count operations like any other operation, 4 times max with 2 sec tim= e out.

"S1 shows a l= ot of Commit Log replay going on. Reading your timeline below this sounds l= ike the auto restart catching you out."

Is there a way to remove this auto-restart while upgrading from t= he Datastax repository on Ubuntu ?

Let= me know if you need something more to understand what happened.

Ala= in

--f46d043be1d44b96d204ced54f0d--