From user-return-35004-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org Tue Jul 2 18:34:57 2013 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 858D0105A0 for ; Tue, 2 Jul 2013 18:34:57 +0000 (UTC) Received: (qmail 44552 invoked by uid 500); 2 Jul 2013 18:34:55 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 44289 invoked by uid 500); 2 Jul 2013 18:34:54 -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 44281 invoked by uid 99); 2 Jul 2013 18:34:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Jul 2013 18:34:53 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of emarshall@pulsepoint.com designates 67.214.159.121 as permitted sender) Received: from [67.214.159.121] (HELO ny-exchange01.pulse.corp) (67.214.159.121) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Jul 2013 18:34:49 +0000 Received: from NY-EXCHANGE01.pulse.corp ([fe80::e14e:2dfc:4f16:c30b]) by ny-exchange01.pulse.corp ([fe80::e14e:2dfc:4f16:c30b%15]) with mapi id 14.02.0328.009; Tue, 2 Jul 2013 14:34:27 -0400 From: Eric Marshall To: "user@cassandra.apache.org" Subject: RE: Does cassandra recover from too many writes? Thread-Topic: Does cassandra recover from too many writes? Thread-Index: Ac53LxJU5F/qES5nTz6Mkb+QG73V8AANwdAAAATcWMA= Date: Tue, 2 Jul 2013 18:34:27 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.1.215.205] Content-Type: multipart/alternative; boundary="_000_D1DA27B3E187F3439F64965092D25439289C748Enyexchange01pul_" MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_D1DA27B3E187F3439F64965092D25439289C748Enyexchange01pul_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Makes sense - I will confirm. Thanks again for the help. Cheers, Eric From: Robert Coli [mailto:rcoli@eventbrite.com] Sent: Tuesday, July 02, 2013 12:53 PM To: user@cassandra.apache.org Subject: Re: Does cassandra recover from too many writes? On Tue, Jul 2, 2013 at 7:18 AM, Eric Marshall > wrote: My query: Should a Cassandra node be able to recover from too many writes = on its own? And if it can, what do I need to do to reach such a blissful st= ate? In general applications running within the JVM are unable to recover when t= he JVM Garbage Collection process has failed in a catastrophic fashion. Thi= s is almost certainly the error condition you are triggering, which is why = your Cassandra node does not recover. To confirm whether this is the case, = enable more verbose GC logging and/or consult existing JVM GC log messages = in system.log. =3DRob --_000_D1DA27B3E187F3439F64965092D25439289C748Enyexchange01pul_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Makes sense – I wil= l confirm.

Thanks again for the help= .

 <= /p>

Cheers,=

  Eric

 <= /p>

From: Robert C= oli [mailto:rcoli@eventbrite.com]
Sent: Tuesday, July 02, 2013 12:53 PM
To: user@cassandra.apache.org
Subject: Re: Does cassandra recover from too many writes?=

 

On Tue, Jul 2, 2013 at 7:18 AM, Eric Marshall <emarshall@pulse= point.com> wrote:

 

My  query: Should a Cassandra node be able to recover from to= o many writes on its own? And if it can, what do I need to do to reach such= a blissful state?

 

In general applications running within the JVM are u= nable to recover when the JVM Garbage Collection process has failed in a ca= tastrophic fashion. This is almost certainly the error condition you are tr= iggering, which is why your Cassandra node does not recover. To confirm whether this is the case, enable more ve= rbose GC logging and/or consult existing JVM GC log messages in system.log.=

 

=3DRob 

--_000_D1DA27B3E187F3439F64965092D25439289C748Enyexchange01pul_--