Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 41715 invoked from network); 20 Dec 2010 22:32:25 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 20 Dec 2010 22:32:25 -0000 Received: (qmail 88261 invoked by uid 500); 20 Dec 2010 22:32:23 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 88236 invoked by uid 500); 20 Dec 2010 22:32:23 -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 88228 invoked by uid 99); 20 Dec 2010 22:32:23 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Dec 2010 22:32:23 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.215.49] (HELO mail-ew0-f49.google.com) (209.85.215.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Dec 2010 22:32:17 +0000 Received: by ewy20 with SMTP id 20so1677980ewy.36 for ; Mon, 20 Dec 2010 14:31:55 -0800 (PST) MIME-Version: 1.0 Received: by 10.213.29.201 with SMTP id r9mr4329969ebc.6.1292884315290; Mon, 20 Dec 2010 14:31:55 -0800 (PST) Received: by 10.213.17.76 with HTTP; Mon, 20 Dec 2010 14:31:55 -0800 (PST) In-Reply-To: References: <4d0fb906.9533e70a.307e.ffffafdb@mx.google.com> Date: Mon, 20 Dec 2010 14:31:55 -0800 Message-ID: Subject: Re: Severe Reliability Problems - 0.7 RC2 From: Chris Goffinet To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=00151748e0265941d40497df161c --00151748e0265941d40497df161c Content-Type: text/plain; charset=ISO-8859-1 What kernel version are you running? I have seen with I/O intense nodes with 2.6.18 to 2.6.24 the kernel has a bug where it locks the JVM and spins to 100%. On Mon, Dec 20, 2010 at 1:14 PM, Brandon Williams wrote: > On Mon, Dec 20, 2010 at 2:13 PM, Dan Hendry wrote: > >> Yes, I have tried that (although only twice). Same impact as a regular >> kill: nothing happens and I get no stacktrace output. It is however on my >> list of things to try again the next time a node dies. I am also not able to >> attach jstack to the process. >> > > Kill -3 will only produce output in foreground mode, jstack will work in > either foreground or background. > > -Brandon > --00151748e0265941d40497df161c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable What kernel version are you running? I have seen with I/O intense nodes wit= h 2.6.18 to 2.6.24 the kernel has a bug where it locks the JVM and spins to= 100%.

On Mon, Dec 20, 2010 at 1:14 PM, B= randon Williams <d= riftx@gmail.com> wrote:
On Mon, Dec 20, 2010 at 2:13 PM, Dan Hendry <dan.hendry.junk@gma= il.com> wrote:

Kill -3 will only produc= e output in foreground mode, jstack will work in either foreground or backg= round.

-Brandon=A0

--00151748e0265941d40497df161c--