RE: Crash by truncate with cassandra 1.1

2012-04-30 Thread Pierre Chalamet
JVM is the latest available after all. Filled CASSANDRA-4201. Thanks, - Pierre From: aaron morton [mailto:aa...@thelastpickle.com] Sent: lundi 30 avril 2012 22:36 To: user@cassandra.apache.org Subject: Re: Crash by truncate with cassandra 1.1 Try upgrading to the newest JVM first

Re: Crash by truncate with cassandra 1.1

2012-04-30 Thread aaron morton
Try upgrading to the newest JVM first. Can you also say what version you were using ? If you still get the problem create a ticket on https://issues.apache.org/jira/browse/CASSANDRA with the steps to reproduce. Please include the OS version, RAM size, JVM information, commit_log_segment_size

RE: Crash by truncate with cassandra 1.1

2012-04-30 Thread Pierre Chalamet
Hi Aaron, No, I just avoid truncating for the moment L (I'm adding CQL prepared statement to Cassandra-Sharp). It's a bit strange anyway, JVM options are: set JAVA_OPTS=-ea^ -javaagent:"%CASSANDRA_HOME%\lib\jamm-0.2.5.jar"^ -Xms1G^ -Xmx1G^ -XX:+HeapDumpOnOutOfMemoryError^ -XX:+UseParN

Re: Crash by truncate with cassandra 1.1

2012-04-29 Thread aaron morton
Did you get a solution on this one ? It looks like you ran out of memory on the machine… > Caused by: java.lang.OutOfMemoryError: Map failed > at sun.nio.ch.FileChannelImpl.map0(Native Method) > ... 7 more cheers - Aaron Morton Freelance Developer @aaronmorton h