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 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
A SIGSEGV is also an indication of hardware issues, which is the first place I would start looking if it were only occurring on one machine. > 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). -- Eric Evans eev...@rackspace.com
