Thanks again for the help. I upgraded my JVM to update 22 but I'm still
getting the same error just as before, and just as, if not more,
frequently. I'm thinking that the best course of action at this point is to
replace the hardware. I would try the test builds, but I can't imagine they
wouldn'
On Oct 14, 2010, at 10:37 PM, Eric Evans wrote:
>> sorry to say, your best bet is to upgrade
>
> I would actually start with some large test builds, kernels work well
> for this. Use a high concurrency (> 4).
Whether or not those fail, assuming x86, download memtest86+ and boot it.
Symptoms li
On Wed, 2010-10-13 at 22:41 -0700, B. Todd Burruss wrote:
> that type of error report indicates a bug in the JVM. something
> that
> should *never* occur if the JVM is operating properly. corrupt
> cassandra data, auto-bootstrapping should never cause that kind of
> crash.
>
> the SIGSEGV in
Alright, very helpful. Thanks again!
That's more encouraging than corruption so I'd be happy to try it.
On Wed, Oct 13, 2010 at 11:41 PM, B. Todd Burruss wrote:
> that type of error report indicates a bug in the JVM. something that
> should *never* occur if the JVM is operating properly. co
that type of error report indicates a bug in the JVM. something that
should *never* occur if the JVM is operating properly. corrupt
cassandra data, auto-bootstrapping should never cause that kind of crash.
the SIGSEGV in the report indicates a segmentation fault
(http://en.wikipedia.org/wik
Thank you Todd. It seems strange though that this is only happening on one
node and has never occurred on any others that are using the same JVM
version. This node was just auto-bootstrapped so do you think this might be
the result of some sort of data corruption? I would like to just
decommissi
you should upgrade to the latest version of the JVM, 1.6.0_21
there was a bug around 1.6.0_18 (or there abouts) that affected cassandra
On 10/13/2010 07:55 PM, Eric Czech wrote:
And this is the java version:
java version "1.6.0_13"
Java(TM) SE Runtime Environment (build 1.6.0_13-b03)
Java Hot
And this is the java version:
java version "1.6.0_13"
Java(TM) SE Runtime Environment (build 1.6.0_13-b03)
Java HotSpot(TM) 64-Bit Server VM (build 11.3-b02, mixed mode)
and it's running on Ubuntu 9.04 (jaunty) linux
4 cores
4 GB RAM
On Wed, Oct 13, 2010 at 8:30 PM, Eric Czech wrote:
> Yea the
Yea there are several. All of them have the same head and it looks like
this:
#
# An unexpected error has been detected by Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x7f140e588b32, pid=2359, tid=139720650078544
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (11.3-b02 mixed mode
linux
is there a jvm crash log file?
On Wed, Oct 13, 2010 at 8:43 PM, Eric Czech wrote:
> Recently, cassandra has been crashing with no apparent error on one specific
> node in my cluster. Has anyone else ever had this happen and is there a way
> to possible figure out what is going on other than look
10 matches
Mail list logo
