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 <[email protected]> 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 the report indicates a segmentation fault ( > http://en.wikipedia.org/wiki/SIGSEGV), which again, should *never* happen > if the JVM is operating properly. the real problem is inside the JVM, not > with Cassandra > > sorry to say, your best bet is to upgrade > > > > On 10/13/2010 10:09 PM, Eric Czech wrote: > > 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 > decommission it but I'm not sure that that would fix the corrupted data (if > it is actually corrupted). Do you know if compact or repair would detect > bad data and disregard it? I'd like to try something like that if possible > before just upgrading the JVM and potentially hiding the real problem. > > On Wed, Oct 13, 2010 at 9:35 PM, B. Todd Burruss <[email protected]>wrote: > >> 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 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 <[email protected]>wrote: >> >>> 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=0x00007f140e588b32, pid=2359, tid=139720650078544 >>> # >>> # Java VM: Java HotSpot(TM) 64-Bit Server VM (11.3-b02 mixed mode >>> linux-amd64) >>> # Problematic frame: >>> # V [libjvm.so+0x1d3b32] >>> # >>> # If you would like to submit a bug report, please visit: >>> >>> Have you ever seen that before? >>> >>> >>> >>> >>> On Wed, Oct 13, 2010 at 7:52 PM, Jonathan Ellis <[email protected]>wrote: >>> >>>> is there a jvm crash log file? >>>> >>>> On Wed, Oct 13, 2010 at 8:43 PM, Eric Czech <[email protected]> >>>> 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 looking at what is >>>> in the >>>> > stdout and system.log files? >>>> > >>>> > Thanks! >>>> > >>>> >>>> >>>> >>>> -- >>>> Jonathan Ellis >>>> Project Chair, Apache Cassandra >>>> co-founder of Riptano, the source for professional Cassandra support >>>> http://riptano.com >>>> >>> >>> >> >
