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 CD10918071 for ; Wed, 16 Dec 2015 00:50:19 +0000 (UTC) Received: (qmail 74700 invoked by uid 500); 16 Dec 2015 00:50:16 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 74655 invoked by uid 500); 16 Dec 2015 00:50:16 -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 74431 invoked by uid 99); 16 Dec 2015 00:50:16 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Dec 2015 00:50:16 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id F41091A0647 for ; Wed, 16 Dec 2015 00:41:25 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.9 X-Spam-Level: ** X-Spam-Status: No, score=2.9 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id at-1rqC6iQ7V for ; Wed, 16 Dec 2015 00:41:16 +0000 (UTC) Received: from mail-vk0-f42.google.com (mail-vk0-f42.google.com [209.85.213.42]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 90B3720C70 for ; Wed, 16 Dec 2015 00:41:15 +0000 (UTC) Received: by mail-vk0-f42.google.com with SMTP id a188so17041069vkc.0 for ; Tue, 15 Dec 2015 16:41:15 -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=g2c3xfLNDUlFUbSBnzbEW7UXEAgSHHMhro1cz7x8VdY=; b=w5+q+N7w6Lzk+iSl3daf8Z4OdTLRhJRFqidHaB1hfPg/oBRoNLPP29Ly8sTdeFCm3w WPqe3lUTuWCnZnJgnC7TKMP6aeAeFPXfCmPIqr83vNyikS6qsOr38yS8G5q7hq3dYiOb dVtb1i1vDPdpw8nZzXvbMvyvUCT85AyTKcKrGHT04IR0Wonuz0Y88EpdjodzNcykvzEF wK0zMr71sBFATQCct5gbLKOtFrUS3KI7Wdhhfgbmm5sJdcfno5ksMd1xqpNp+qjl2FCd SUDoFdlSO+SUH4j9S5OMn8QjEJf6F6Jxj73Dz2ugkpYlJu6ICXxv8x4klGSvavKNTcic 5TeA== MIME-Version: 1.0 X-Received: by 10.31.128.138 with SMTP id b132mr3245220vkd.14.1450226474294; Tue, 15 Dec 2015 16:41:14 -0800 (PST) Received: by 10.31.47.137 with HTTP; Tue, 15 Dec 2015 16:41:14 -0800 (PST) In-Reply-To: References: <0CAA1D64-4C66-429D-AF72-EB88904AACEF@crowdstrike.com> Date: Tue, 15 Dec 2015 19:41:14 -0500 Message-ID: Subject: Re: Unable to start one Cassandra node: OutOfMemoryError From: Jack Krupansky To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=001a114271acd84f8f0526f929b3 --001a114271acd84f8f0526f929b3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Can a core Cassandra committer verify if removing the compactions_in_progre= ss folder is indeed to desired and recommended solution to this problem, or whether it might in fact be a bug that this workaround is needed at all? Thanks! -- Jack Krupansky On Thu, Dec 10, 2015 at 5:34 PM, Mikhail Strebkov wrote: > Steve, thanks a ton! Removing compactions_in_progress helped! Now the nod= e > 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 = 32GB 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 fil= es >> 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 comman= d and >> wait for the compactions to finish. >> >> Last time we hit it =E2=80=93 was due to testing HA when we forced kille= d 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 >> instead. >> >> >> >> 71% of your heap is collections =E2=80=93 may be a weird data model quir= k, 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 a= ll >> 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 recei= ved >> 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 emai= l >> or its attachments. >> > > --001a114271acd84f8f0526f929b3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Can a core Cassandra committer verify if removing the=C2= =A0compactions_in_progress folder is indee= d to desired and recommended solution to this problem, or whether it might = in fact be a bug that this workaround is needed at all? Thanks!

-- Jack Krupansky

On Thu, Dec 10, 2015 at 5:34 PM, Mikhail Str= ebkov <strebkov@gmail.com> wrote:
Steve,=C2=A0thanks 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 confu= sed.

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.


--001a114271acd84f8f0526f929b3--