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 david.daeschler@gmail.com
 designates 74.125.82.44 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <2AF22870-3959-47DF-83C9-AADC37610800@bloomdigital.com>
References: <2AF22870-3959-47DF-83C9-AADC37610800@bloomdigital.com>
Date: Sat, 30 Jun 2012 23:57:20 -0400
Message-ID: 
 <CA+SkF=JDioN3uKETkD9oagKDJGF+sBWRabf5KA=McpnwFsqxgQ@mail.gmail.com>
Subject: Re: High CPU usage as of 8pm eastern time
From: David Daeschler <david.daeschler@gmail.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1

YES!

This happened to me as well. RUNNING THAT COMMAND FIXED THE PROBLEM!

THANK YOU SO MUCH


On Sat, Jun 30, 2012 at 11:11 PM, Mina Naguib
<mina.naguib@bloomdigital.com> wrote:
>
> Hi folks
>
> Our cassandra (and other java-based apps) started experiencing extremely high CPU usage as of 8pm eastern time (midnight UTC).
>
> The issue appears to be related to specific versions of java + linux + ntpd
>
> There are many solutions floating around on IRC, twitter, stackexchange, LKML.
>
> The simplest one that worked for us is simply to run this command on each affected machine:
>
> date; date `date +"%m%d%H%M%C%y.%S"`; date;
>
> CPU drop was instantaneous - there was no need to restart the server, ntpd, or any of the affected JVMs.
>
>
>


-- 
David Daeschler