cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Evans <eev...@acunu.com>
Subject Re: Cassandra upgrade 1.1.4 issue
Date Fri, 24 Aug 2012 15:50:44 GMT
On Fri, Aug 24, 2012 at 5:00 AM, Adeel Akbar
<adeel.akbar@panasiangroup.com> wrote:
> I have upgraded cassandra on ring and one node successfully upgraded first
> node. On second node I got following error. Please help me to resolve this
> issue.
>
> [root@XXXXX]# /u/cassandra/apache-cassandra-1.1.4/bin/cassandra -f
> xss =  -ea
> -javaagent:/u/cassandra/apache-cassandra-1.1.4/bin/../lib/jamm-0.2.5.jar
> -XX:+UseThreadPriorities -XX:ThreadPriorityPolicy=42 -Xms502M -Xmx502M
> -Xmn100M -XX:+HeapDumpOnOutOfMemoryError -Xss128k
> Segmentation fault

Segmentation faults can be caused by software bugs, or by faulty
hardware.  If it is a software bug, it's very unlikely to be a
Cassandra bug (there should be nothing we could do to cause a JVM
segfault).

I would take a close look at what is different between these two
hosts, starting with the version of JVM.  If you have a core dump,
that might provide some insight (and if you don't, it wouldn't hurt to
get one).

Cheers,

-- 
Eric Evans
Acunu | http://www.acunu.com | @acunu

Mime
View raw message