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 55EA518295 for ; Thu, 10 Dec 2015 22:34:50 +0000 (UTC) Received: (qmail 82520 invoked by uid 500); 10 Dec 2015 22:34:47 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 82475 invoked by uid 500); 10 Dec 2015 22:34:47 -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 82465 invoked by uid 99); 10 Dec 2015 22:34:47 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Dec 2015 22:34:47 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 5F5EEC0F42 for ; Thu, 10 Dec 2015 22:34:47 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 4.099 X-Spam-Level: **** X-Spam-Status: No, score=4.099 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, KAM_LINEPADDING=1.2, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id PkbrOiDnauqj for ; Thu, 10 Dec 2015 22:34:38 +0000 (UTC) Received: from mail-qg0-f49.google.com (mail-qg0-f49.google.com [209.85.192.49]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id A7FF1429C4 for ; Thu, 10 Dec 2015 22:34:37 +0000 (UTC) Received: by qgcc31 with SMTP id c31so168102390qgc.3 for ; Thu, 10 Dec 2015 14:34:31 -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=yaW3iWEJppVRA9CvuF3CXkmZOeUeQAa5bnkAycVLEcg=; b=wf+rXjaQuS1rWk4iMiCkRYDuCDxE/YX9lPP1yHnwi79dzPjQMiY/+cTJJ5SMw3Jpvl 9PcxBAIRDdwd7UwnpAGzvRnOs5aUBQ0qK3wc0Gvji2n8byWH9nsF9WpREkyIM2OMFagk QexgL78OkoFxMAY6A42U0Rdkt6DbRnQD26kESmlxg5f8PTAAN5YejrGA3RYvND5Z+Tgg iQSSQHhFw2/aXAxP//qVU2vkblXFUVgWbWiqXO65kYK6467UyYgzO5511KKr3xG4GG/1 qsVpdmNArK3iInRF4JvnWmLfNqRY/EbJ4Vlm60gIRBYZphg2dBgVmLJYIo8/HS2ckd0k qURA== MIME-Version: 1.0 X-Received: by 10.140.246.195 with SMTP id r186mr10471956qhc.56.1449786871710; Thu, 10 Dec 2015 14:34:31 -0800 (PST) Received: by 10.233.223.70 with HTTP; Thu, 10 Dec 2015 14:34:31 -0800 (PST) In-Reply-To: References: <0CAA1D64-4C66-429D-AF72-EB88904AACEF@crowdstrike.com> Date: Thu, 10 Dec 2015 14:34:31 -0800 Message-ID: Subject: Re: Unable to start one Cassandra node: OutOfMemoryError From: Mikhail Strebkov To: "user@cassandra.apache.org" Content-Type: multipart/alternative; boundary=001a1139be3e7d0b69052692cf8c --001a1139be3e7d0b69052692cf8c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Steve, thanks a ton! Removing compactions_in_progress helped! Now the node is running again. p.s. Sorry for referring to you by the last name in my last email, I got confused. On Thu, Dec 10, 2015 at 2:09 AM, Walsh, Stephen wrote: > 8GB is the max recommended for heap size and that=E2=80=99s if you have 3= 2GB or > more available. > > > > We use 6GB on our 16GB machines and its very stable > > > > The out of memory could be coming from cassandra reloading > compactions_in_progress into memory, you can check this from the log file= s > if needs be. > > You can safely delete this folder inside the data directory. > > > > This can happen if you didn=E2=80=99t stop cassandra with a drain command= and wait > for the compactions to finish. > > Last time we hit it =E2=80=93 was due to testing HA when we forced killed= an > entire cluster. > > > > Steve > > > > > > > > *From:* Jeff Jirsa [mailto:jeff.jirsa@crowdstrike.com] > *Sent:* 10 December 2015 02:49 > *To:* user@cassandra.apache.org > *Subject:* Re: Unable to start one Cassandra node: OutOfMemoryError > > > > 8G is probably too small for a G1 heap. Raise your heap or try CMS instea= d. > > > > 71% of your heap is collections =E2=80=93 may be a weird data model quirk= , but try > CMS first and see if that behaves better. > > > > > > > > *From: *Mikhail Strebkov > *Reply-To: *"user@cassandra.apache.org" > *Date: *Wednesday, December 9, 2015 at 5:26 PM > *To: *"user@cassandra.apache.org" > *Subject: *Unable to start one Cassandra node: OutOfMemoryError > > > > Hi everyone, > > > > While upgrading our 5 machines cluster from DSE version 4.7.1 (Cassandra > 2.1.8) to DSE version: 4.8.2 (Cassandra 2.1.11) one of the nodes can't > start with OutOfMemoryError. > > We're using HotSpot 64-Bit Server VM/1.8.0_45 and G1 garbage collector > with 8 GiB heap. > > Average node size is 300 GiB. > > > > I looked at the heap dump with YourKit profiler (www.yourkit.com) and it > was quite hard since it's so big, but can't get much out of it: > http://i.imgur.com/fIRImma.png > > > > As far as I understand the report, there are 1,332,812 instances of > org.apache.cassandra.db.Row which retain 8 GiB. I don't understand why al= l > of them are still strongly reachable? > > > > Please help me to debug this. I don't know even where to start. > > I feel very uncomfortable with 1 node running 4.8.2, 1 node down and 3 > nodes running 4.7.1 at the same time. > > > > Thanks, > > Mikhail > > > > > This email (including any attachments) is proprietary to Aspect Software, > Inc. and may contain information that is confidential. If you have receiv= ed > this message in error, please do not read, copy or forward this message. > Please notify the sender immediately, delete it from your system and > destroy any copies. You may not further disclose or distribute this email > or its attachments. > --001a1139be3e7d0b69052692cf8c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Steve,=C2=A0thanks a ton! Removing compactions_in_progress= helped! Now the node is running again.

p.s. Sorry f= or referring to you by the last name in my last email, I got confused.

On Thu, Dec 10, = 2015 at 2:09 AM, Walsh, Stephen <Stephen.Walsh@aspect.com> wrote:

8GB is the max recommended for heap s= ize and that=E2=80=99s if you have 32GB or more available.

=C2=A0

We use 6GB on our 16GB machines and i= ts very stable

=C2=A0

The out of memory could be coming fro= m cassandra reloading compactions_in_progress into memory, you can check th= is from the log files if needs be.

You can safely delete this folder ins= ide the data directory.

=C2=A0

This can happen if you didn=E2=80=99t= stop cassandra with a drain command and wait for the compactions to finish= .

Last time we hit it =E2=80=93 was due= to testing HA when we forced killed an entire cluster.

=C2=A0

Steve

=C2=A0

=C2=A0

=C2=A0

From: = Jeff Jirsa [mailto:jeff.jirsa@crowdstrike.com]
Sent: 10 December 2015 02:49
To: u= ser@cassandra.apache.org
Subject: Re: Unable to start one Cassandra node: OutOfMemoryError=

=C2=A0

8G is probably too small for a G1 heap.= Raise your heap or try CMS instead.

=C2=A0

71% of your heap is collections =E2=80= =93 may be a weird data model quirk, but try CMS first and see if that beha= ves better.

=C2=A0

=C2=A0

=C2=A0

From: Mikhail Strebkov
Reply-To: "user@cassandra.apache.org"
Date: Wednesday, December 9, 2015 at 5:26 PM
To: "user@cassandra.apache.org"
Subject: Unable to start one Cassandra node: OutOfMemoryError=

=C2=A0

Hi everyone,

=C2=A0

While upgrading our 5 machines cluster = from DSE version 4.7.1 (Cassandra 2.1.8) to DSE version: 4.8.2 (Cassandra 2= .1.11) =C2=A0one of the nodes can't start with OutOfMemoryError.

We're using HotSpot 64-Bit Server VM/1.8.0_45 and G1 garbage collector = with 8 GiB heap.

Average node size is 300 GiB.

=C2=A0

I looked at the heap dump with YourKit = profiler (www.yourkit.= com) and it was quite hard since it's so big, but can't get muc= h out of it:=C2=A0http://i.imgur.com/fIRImma.png

=C2=A0

As far as I understand the report, ther= e are 1,332,812 instances of org.apache.cassandra.db.Row which retain 8 GiB= . I don't understand why all of them are still strongly reachable?

=C2=A0

Please=C2=A0help me to debug this. I do= n't know even where to start.

I feel very uncomfortable with 1 node r= unning 4.8.2, 1 node down and 3 nodes running 4.7.1 at the same time.

=C2=A0

Thanks,

Mikhail

=C2=A0

=C2=A0

This email (including any attachments) is proprietary to Aspect Software, I= nc. and may contain information that is confidential. If you have received = this message in error, please do not read, copy or forward this message. Pl= ease notify the sender immediately, delete it from your system and destroy any copies. You may not further dis= close or distribute this email or its attachments.

--001a1139be3e7d0b69052692cf8c--