Well Romain, I had tried restarting the VM as well but problem still
remained.
What I noticed is after sometime irrespective I run cassandra from other
user or using the normal cassandra the problem still remains. As soon as it
starts, the JVM is get killed because of memory issue. Is there some other
settings other then limits.conf file I need to configure.
Also to note that I dont have a /etc/limits.d/cassandra.conf file. I just
configured them in limits.conf. Even though I made same the group ID of
both the users(cassanda, X) but no use. Is there anything like cassandra
has to be started under cassandra user only? What are the special
configurations required if we try to run cassandra under a different user?
Thanks
Dev
On Tue, May 20, 2014 at 10:44 PM, Romain HARDOUIN romain.hardo...@urssaf.fr
wrote:
Well... you have already changed the limits ;-)
Keep in mind that changes in the limits.conf file will not affect
processes that are already running.
opensaf dev opensaf...@gmail.com a écrit sur 21/05/2014 06:59:05 :
De : opensaf dev opensaf...@gmail.com
A : user@cassandra.apache.org,
Date : 21/05/2014 07:00
Objet : Memory issue
Hi guys,
I am trying to run Cassandra on CentOS as an user X other then root
or cassandra. When I run as user cassandra, it starts and runs fine.
But, when I run under user X, I am getting the below error once
cassandra started and system freezes totally.
Insufficient memlock settings:
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.
I have tried the tips available online to change the memlock and
other limits both for users cassadra and X, but did not solve the
problem.
What else I should consider when I run cassandra other then user
cassandra/root.
Any help is much appreciated.
Thanks
Dev