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 4ECEA18139 for ; Thu, 10 Dec 2015 22:20:47 +0000 (UTC) Received: (qmail 33126 invoked by uid 500); 10 Dec 2015 22:20:45 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 33078 invoked by uid 500); 10 Dec 2015 22:20:45 -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 33068 invoked by uid 99); 10 Dec 2015 22:20:45 -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:20:45 +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 918C9C0FFD for ; Thu, 10 Dec 2015 22:20:44 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.001 X-Spam-Level: *** X-Spam-Status: No, score=3.001 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=3, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=pythian-com.20150623.gappssmtp.com Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id KEvlyMZb6ga7 for ; Thu, 10 Dec 2015 22:20:30 +0000 (UTC) Received: from mail-io0-f176.google.com (mail-io0-f176.google.com [209.85.223.176]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id 4945526621 for ; Thu, 10 Dec 2015 22:20:30 +0000 (UTC) Received: by ioc74 with SMTP id 74so107929588ioc.2 for ; Thu, 10 Dec 2015 14:20:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pythian-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=H60WsagWVO9FQuJ55Y+lNAIiPuC2DA5dVkPhNTyMrkU=; b=EI5FWifFcDfw45830HUT/ey7dRvtXTSbJupCSuK+aaaM7DEM84ZA9ACHu+8deImNBI 9fU2l5okaFOx5JdpwYfVMu4wrz/WT8LeqpFyiSlnj3ikq4I06cv68tzWtI7MIkIo+7pw u5vy2B6xYrenkS9A4yABjj5WE3ZwXfGBJfhn1aF2RPC9SlGKt84bbZBfH0Ic68AyBsoa NlZ1FkisLQRzo8+ejA/4Wk9oEYdgtP6na5Ct7SapP7Dl18YaRIbMLkKWvpt6fquxsk6A r5xk6tytZNZ24wj9yzwbL654xYqIqouoJe+lo0PVkOvZU0JAjbkyrXCP5CIV9w6N6mqq BFag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=H60WsagWVO9FQuJ55Y+lNAIiPuC2DA5dVkPhNTyMrkU=; b=aD2JcH5aedj4KkBHzVzuUni8E1vTlHwCrCeuqur0EWb6IuAPxgqupZpdQ6Co2Im/54 PSkIfg5LrwwaKBL+/nIRkEDSL5iVTmtpg+i+dhvwmLGkbvIubR5f52CFpUZ21cksXm9s MhdoXJdIMOIVvaUfrIFs1kdBK/nm4I16YDgn7s/Iec/ynVDW1Vxh+URhv06YEfCo/eB9 vBvdnoij8ChkrH0xEmE7lQ9zhjOP7qyBNIuIq08DmR5xMVj9bsw65UtWGGDbOXwj//pp doPtXG0Pcl21Cpm8n8FM5Zj3KxMYHIUYvEUDPad6JF+k9e+xzOxHkpMFLkN8V56Nhbkz WHow== X-Gm-Message-State: ALoCoQlxjZ5DDAwFnv4z0di6G0JUH6qjElNluDenhoME2lJXN8Y/riVIEA4E5eUUsoWgW2WonqL1HEKOu3SRapmYpSb3pU05HE4n3iVolBxjsunpsEE6dmIQKdo0FEK34Pb5MBHYDqIQgkuRPYc/cIHy2DckznOIhWaklHFAypAbrdr4YJcFR08= X-Received: by 10.107.135.65 with SMTP id j62mr15525791iod.47.1449786029536; Thu, 10 Dec 2015 14:20:29 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.235.144 with HTTP; Thu, 10 Dec 2015 14:20:10 -0800 (PST) In-Reply-To: References: <0CAA1D64-4C66-429D-AF72-EB88904AACEF@crowdstrike.com> From: Carlos Rolo Date: Thu, 10 Dec 2015 22:20:10 +0000 Message-ID: Subject: Re: Unable to start one Cassandra node: OutOfMemoryError To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=001a113ecbf24a9e980526929db2 --001a113ecbf24a9e980526929db2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Dealt with that recently, and the only solution that made it work was to increase heap sizes. Regards, Carlos Juzarte Rolo Cassandra Consultant Pythian - Love your data rolo@pythian | Twitter: @cjrolo | Linkedin: *linkedin.com/in/carlosjuzarter= olo * Mobile: +351 91 891 81 00 | Tel: +1 613 565 8696 x1649 www.pythian.com On Thu, Dec 10, 2015 at 10:14 PM, Mikhail Strebkov wrote: > Jeff, CMS GC didn't help. Thinking about it, I don't see how can it help > if there are 8GB of strongly reachable objects from the GC roots. > > Walsh, thanks for your suggestion, I checked the log and there are some > compactions_in_progress but total size of those is ~300 MiB as far as I > understand. > > Here is the log of the last unsuccessful start: > https://gist.github.com/kluyg/7b9955d34def947f5e0a > > > 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. >> > > --=20 -- --001a113ecbf24a9e980526929db2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Dealt with that recently, and the only solution that made = it work was to increase heap sizes.



Regards,
Carlos Juzarte Rolo
Cassandra Consultant
= =C2=A0
Pythian - Love your data

rolo@pyt= hian | Twitter: @cjrolo | Linkedin: linkedin.com/in/= carlosjuzarterolo
Mobile: +351 91 891 81 00 | Tel:= +1 613 565 8696 x1649
=

On Thu, Dec 10, 2015 at 10:14 PM, Mikhail St= rebkov <strebkov@gmail.com> wrote:
Jeff, CMS GC didn't help. Thinking about= it, I don't see how can it help if there are 8GB of strongly reachable= objects from the GC roots.

Walsh, thanks for your suggestion, I che= cked the log and there are some compactions_in_progress but total size of t= hose is ~300 MiB as far as I understand.

Here is the log= of the last=C2=A0unsuccessful=C2=A0start:=C2=A0https://gist.github.c= om/kluyg/7b9955d34def947f5e0a


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

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

=C2=A0

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

=C2=A0

The out of memory could be coming from cassa= ndra reloading compactions_in_progress into memory, you can check this from= the log files if needs be.

You can safely delete this folder inside the= data directory.

=C2=A0

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

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

=C2=A0

Steve

=C2=A0

=C2=A0

=C2=A0

From: Jeff Jirsa [mailto:jeff.jirsa@crowdst= rike.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 behaves better.

=C2=A0

=C2=A0

=C2=A0

From: Mikha= il 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 ver= sion 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 much out of it:=C2=A0http://i.imgur.com/fIRImma.png

=C2=A0

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 all of them are still strongly reachable?

=C2=A0

Please=C2=A0help 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.

=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.



--



--001a113ecbf24a9e980526929db2--