Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of sdolgy@gmail.com designates
 209.85.220.172 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=wJmCc+OQ2SBOErQnoMhVheXJfiZer0nCMPDsgN1cML/Pvc6/5Mi4NSjWGT1EjmBJkw
         LZr3FAXb2qd7A+5towfTtJGln4THWXNngFUj7q66/uvBrSsCzmueI48d1tf8ZFNVGooc
         6tJc4Gdq5vn7HZ67R2NyeaycaghPZh8AvoF9g=
MIME-Version: 1.0
In-Reply-To: <BANLkTim+RXfFrajR2cwsU_6yS3xdfbRxkQ@mail.gmail.com>
References: <BANLkTimX6a2WFsU-OTpFwnvSu5KiXrYuaA@mail.gmail.com>
 <BANLkTi=xWEPj+v98ouv7v+WxEGK3uR6aFQ@mail.gmail.com>
 <BANLkTim+RXfFrajR2cwsU_6yS3xdfbRxkQ@mail.gmail.com>
From: Sasha Dolgy <sdolgy@gmail.com>
Date: Wed, 22 Jun 2011 14:53:37 +0200
Message-ID: <BANLkTim2oJcT+Sp0iEhmU-SgD7sZgktRPg@mail.gmail.com>
Subject: Re: OOM (or, what settings to use on AWS large?)
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Yes ... this is because it was the OS that killed the process, and
wasn't related to Cassandra "crashing".  Reviewing our monitoring, we
saw that memory utilization was pegged at 100% for days and days
before it was finally killed because 'apt' was fighting for resource.
At least, that's as far as I got in my investigation before giving up,
moving to 0.8.0 and implementing 24hr nodetool repair on each node via
cronjob....so far ... no problems.

On Wed, Jun 22, 2011 at 2:49 PM, William Oberman
<oberman@civicscience.com> wrote:
> Well, I managed to run 50 days before an OOM, so any changes I make will
> take a while to test ;-) =A0I've seen the=A0GCInspector log lines appear
> periodically in my logs, but I didn't see a correlation with the crash.
> I'll read the instructions on how to properly do a rolling upgrade today,
> practice on test, and try that on production first.
> will