cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alaa Zubaidi (PDF)" <>
Subject Re: Cassandra 2.2.1 stuck at 100% on Windows
Date Fri, 16 Oct 2015 17:02:22 GMT
Thanks Rob,

No OOM in any of the log files, and NO long GC at that time.
I attached the last 2 minutes before it hangs until we restart cassandra
after hour an half.

On Thu, Oct 15, 2015 at 6:29 PM, Robert Coli <> wrote:

> On Thu, Oct 15, 2015 at 6:04 PM, Alaa Zubaidi (PDF) <>
> wrote:
>> We are running Cassandra 2.2.1 on Windows 2008R2, and we see that
>> multiple Nodes are stuck at 99% CPU bringing the whole VM to a halt.
>> We suspect that there is another process that IT/Windows is causing the
>> CPU issue, but the problem is Cassandra does NOT recover, the CPU
>> utilization start climbing until the VM is not usable. If we restart
>> Cassandra, things go back to normal.
> Most cases where a JVM does not recover and churns at maxed CPU are the
> result of GC failure and/or OOM.
> Check your logs for OOM and long GCs.
> Also FWIW you are among a relatively small group of Windows operators.
> Other than with the people working at datastax to support Windows, there is
> not a whole lot of well understood operational best practice for Cassandra
> on Windows.
> =Rob


Alaa Zubaidi
PDF Solutions, Inc.
333 West San Carlos Street, Suite 1000
San Jose, CA 95110  USA
Tel: 408-283-5639
fax: 408-938-6479

*This message may contain confidential and privileged information. If it 
has been sent to you in error, please reply to advise the sender of the 
error and then immediately permanently delete it and all attachments to it 
from your systems. If you are not the intended recipient, do not read, 
copy, disclose or otherwise use this message or any attachments to it. The 
sender disclaims any liability for such unauthorized use. PLEASE NOTE that 
all incoming e-mails sent to PDF e-mail accounts will be archived and may 
be scanned by us and/or by external service providers to detect and prevent 
threats to our systems, investigate illegal or inappropriate behavior, 
and/or eliminate unsolicited promotional e-mails (“spam”). If you have any 
concerns about this process, please contact us at *
** <>*.*

View raw message