[
https://issues.apache.org/jira/browse/CASSANDRA-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067852#comment-13067852
]
paul cannon commented on CASSANDRA-2845:
----------------------------------------
Ok, I believe I've reproduced this. I don't get 100% cpu usage, but I do see
strange stalls and kernel errors in dmesg about tasks being hung for too long,
or in some cases, the machine becomes completely unresponsive. Simple things
like "ps aux" hang on reading certain /proc/$pid/cmdline entries, effects like
that.
What I've found so far:
* Can reproduce on Ubuntu 11.04 (natty), haven't been able to reproduce on
Ubuntu 10.10 (maverick)
* Can reproduce with several different libjna-java/jna.jar builds. Can not
reproduce without any JNA available.
* Can not reproduce when CLibrary.tryMlockall() call to mlockall() is commented
out.
* Can still reproduce when memlock resource-limit is severely restricted (i.e.
set to 1 kb in /etc/security/limits.d/cassandra.conf)
* Can reproduce with a couple different EC2 kernel images. Haven't found a
kernel yet that makes it unreproducible.
At this point I'm suspecting some sort of funkiness in the natty glibc. Will be
testing more.
Oh, and as an aside- aptitude also doesn't force you to install recommends;
just use {{aptitude install --without-recommends}}.
> Cassandra uses 100% system CPU on Ubuntu Natty (11.04)
> ------------------------------------------------------
>
> Key: CASSANDRA-2845
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2845
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.8.0
> Environment: Default install of Ubuntu 11.04
> Reporter: Steve Corona
> Assignee: paul cannon
> Priority: Critical
> Fix For: 0.8.2
>
>
> Step 1. Boot up a brand new, default Ubuntu 11.04 Server install
> Step 2. Install Cassandra from Apache APT Respository (deb
> http://www.apache.org/dist/cassandra/debian 08x main)
> Step 3. apt-get install cassandra, as soon as it cassandra starts it will
> freeze the machine
> What's happening is that as soon as cassandra starts up it immediately sucks
> up 100% of CPU and starves the machine. This effectively bricks the box until
> you boot into single user mode and disable the cassandra init.d script.
> Under htop, the CPU usage shows up as "system" cpu, not user.
> The machine I'm testing this on is a Quad-Core Sandy Bridge w/ 16GB of
> Memory, so it's not a system resource issue. I've also tested this on
> completely different hardware (Dual 64-Bit Xeons & AMD X4) and it has the
> same effect.
> Ubuntu 10.10 does not exhibit the same issue. I have only tested 0.8 and
> 0.8.1.
> root@cassandra01:/# java -version
> java version "1.6.0_22"
> OpenJDK Runtime Environment (IcedTea6 1.10.2) (6b22-1.10.2-0ubuntu1~11.04.1)
> OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode)
> root@cassandra:/# uname -a
> Linux cassandra01 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC
> 2011 x86_64 x86_64 x86_64 GNU/Linux
> /proc/cpu
> Intel(R) Xeon(R) CPU E31270 @ 3.40GHz
> /proc/meminfo
> MemTotal: 16459776 kB
> MemFree: 14190708 kB
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
