> As soon as it starts, the JVM is get killed because of memory issue. What is the memory issue that gets kills the JVM ?
The log message below is simply a warning > WARN [main] 2011-06-15 09:58:56,861 CLibrary.java (line 118) Unable to lock > JVM memory (ENOMEM). > This can result in part of the JVM being swapped out, especially with mmapped > I/O enabled. > Increase RLIMIT_MEMLOCK or run Cassandra as root. Is there anything in the system logs ? Cheers Aaron ----------------- Aaron Morton New Zealand @aaronmorton Co-Founder & Principal Consultant Apache Cassandra Consulting http://www.thelastpickle.com On 24/05/2014, at 9:17 am, Robert Coli <rc...@eventbrite.com> wrote: > On Fri, May 23, 2014 at 2:08 PM, opensaf dev <opensaf...@gmail.com> wrote: > I have a different service which controls the cassandra service for high > availability. > > IMO, starting or stopping a Cassandra node should never be a side effect of > another system's properties. YMMV. > > https://issues.apache.org/jira/browse/CASSANDRA-2356 > > For some related comments. > > =Rob >
