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 A7F281035B for ; Thu, 19 Dec 2013 13:33:14 +0000 (UTC) Received: (qmail 33460 invoked by uid 500); 19 Dec 2013 13:33:07 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 33438 invoked by uid 500); 19 Dec 2013 13:33:04 -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 33428 invoked by uid 99); 19 Dec 2013 13:33:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Dec 2013 13:33:01 +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 (nike.apache.org: domain of comomore@gmail.com designates 209.85.128.52 as permitted sender) Received: from [209.85.128.52] (HELO mail-qe0-f52.google.com) (209.85.128.52) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Dec 2013 13:32:54 +0000 Received: by mail-qe0-f52.google.com with SMTP id ne12so927615qeb.25 for ; Thu, 19 Dec 2013 05:32:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=tTL2d6GVNlcv/nHmWDwS6MWfF4Q2N0tb2c5vyniMkI8=; b=RYIc1Wia20FNshkPc2hTgfy/B9kePRJ6WTmLS7ehXOQ17mKiqxXaStVRo9bMrp8fqt MVoWsp4/0n0kFvSQhpQ5uagRlHotAVMoCfLKDcXFrSAHH4n1UOTXAbS7ASmf4l/YN97P FJkuI19yiq95i7Ory5FMkknNO7vSRYrvOqZqmvkpCL+VHIKkAHdvNxOpfrrsyuEiiy4y 1MCNpiHogjEj9Q1g1oysD8/Mnj5WGAPhc4WvOr07Toso+NcAqg4qX9uQ9YpJC1pRpGCx y1EA7LH7TL8AgXijGli18zMUrjov0nhaXzk5ETJA3An8/HX5f4+vddXfUTJQzMiJ5h7q LlFg== MIME-Version: 1.0 X-Received: by 10.49.2.132 with SMTP id 4mr2771755qeu.15.1387459953898; Thu, 19 Dec 2013 05:32:33 -0800 (PST) Received: by 10.96.62.170 with HTTP; Thu, 19 Dec 2013 05:32:33 -0800 (PST) In-Reply-To: References: Date: Thu, 19 Dec 2013 07:32:33 -0600 Message-ID: Subject: Re: MUTATION messages dropped From: srmore To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=047d7b6d99b0b139b904ede3313f X-Virus-Checked: Checked by ClamAV on apache.org --047d7b6d99b0b139b904ede3313f Content-Type: text/plain; charset=ISO-8859-1 What version of Cassandra are you running ? I used to see them a lot with 1.2.9, I could correlate the dropped messages with the heap usage almost every time, so check in the logs whether you are getting GC'd. In this respect 1.2.12 appears to be more stable. Moving to 1.2.12 took care of this for us. Thanks, Sandeep On Thu, Dec 19, 2013 at 6:12 AM, Alexander Shutyaev wrote: > Hi all! > > We've had a problem with cassandra recently. We had 2 one-minute periods > when we got a lot of timeouts on the client side (the only timeouts during > 9 days we are using cassandra in production). In the logs we've found > corresponding messages saying something about MUTATION messages dropped. > > Now, the official faq [1] says that this is an indicator that the load is > too high. We've checked our monitoring and found out that 1-minute average > cpu load had a local peak at the time of the problem, but it was like 0.8 > against 0.2 usual which I guess is nothing for a 2 core virtual machine. > We've also checked java threads - there was no peak there and their count > was reasonable ~240-250. > > Can anyone give us a hint - what should we monitor to see this "high load" > and what should we tune to make it acceptable? > > Thanks in advance, > Alexander > > [1] http://wiki.apache.org/cassandra/FAQ#dropped_messages > --047d7b6d99b0b139b904ede3313f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
What version of Cassandra are you running ? I used to= see them a lot with 1.2.9, I could correlate the dropped messages with the= heap usage almost every time, so check in the logs whether you are getting= GC'd. In this respect 1.2.12 appears to be more stable. Moving to 1.2.= 12 took care of this for us.

Thanks,
Sandeep
<= br>
On Thu, Dec 19, 2013 at 6:12 AM, Alexande= r Shutyaev <shutyaev@gmail.com> wrote:
Hi all!

= We've had a problem with cassandra recently. We had 2 one-minute period= s when we got a lot of timeouts on the client side (the only timeouts durin= g 9 days we are using cassandra in production). In the logs we've found= corresponding messages saying something about MUTATION messages dropped.

Now, the official faq [1] says that this is an indicato= r that the load is too high. We've checked our monitoring and found out= that 1-minute average cpu load had a local peak at the time of the problem= , but it was like 0.8 against 0.2 usual which I guess is nothing for a 2 co= re virtual machine. We've also checked java threads - there was no peak= there and their count was reasonable ~240-250.

Can anyone give us a hint - what should we monitor to s= ee this "high load" and what should we tune to make it acceptable= ?

Thanks in advance,
Alexander


--047d7b6d99b0b139b904ede3313f--