Re: java.lang.InternalError: a fault occurred in a recent unsafe memory access operation in compiled Java code

try different jvm version or find out why is that happening? hth jason On Mon, May 4, 2015 at 10:10 AM, 曹志富 wrote: > Hi guys: > > I havle C* 2.1.3 cluster,25 nodes ,running in JDK_1.7.0_71, CentOS > 2.6.32-220.el6.x86_64,4 Core,32GB RAM. > > Today one of the nodes,has some error like this: > >

java.lang.InternalError: a fault occurred in a recent unsafe memory access operation in compiled Java code

Hi guys: I havle C* 2.1.3 cluster,25 nodes ,running in JDK_1.7.0_71, CentOS 2.6.32-220.el6.x86_64,4 Core,32GB RAM. Today one of the nodes,has some error like this: java.lang.InternalError: a fault occurred in a recent unsafe memory access operation in compiled Java code at org.apache.cassandra.i

Re: Denormalization leads to terrible, rather than better, Cassandra performance -- I am really puzzled

Hello, there. In relation to the Java driver, I would recommend updating to the latest version as there were a lot of issues reported in versions earlier that 2.0.9 were the driver is incorrectly marking nodes as down/not available. In fact, there is a new version of the driver being released in

Re: Query returning tombstones

Hi Jens, thanks a lot for the link! Your ticket seems very similar to my request. kind regards, Christian On Sat, May 2, 2015 at 2:25 PM, Jens Rantil wrote: > Hi Christian, > > I just know Sylvain explicitly stated he wasn't a fan of exposing > tombstones here: > https://issues.apache.org/jir