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
On Wed, May 21, 2014 at 12:59 AM, opensaf dev opensaf...@gmail.com wrote:
When I run as user cassandra, it starts and runs fine.
Why do you want to run Cassandra as a different user?
--
Patricia Gorla
@patriciagorla
Consultant
Apache Cassandra Consulting
http://www.thelastpickle.com
I have a different service which controls the cassandra service for high
availability.
Thanks
Dev
On Fri, May 23, 2014 at 7:35 AM, Patricia Gorla
patri...@thelastpickle.comwrote:
On Wed, May 21, 2014 at 12:59 AM, opensaf dev opensaf...@gmail.comwrote:
When I run as user cassandra, it
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.
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
Hi,
You have to define limits for the user.
Here is an example for the user cassandra:
# cat /etc/security/limits.d/cassandra.conf
cassandra - memlock unlimited
cassandra - nofile 10
best,
Romain
opensaf dev opensaf...@gmail.com a écrit sur 21/05/2014 06:59:05 :
De :
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
-06-05, at 2:56 PM, Poziombka, Wade L wrote:
Alas, upgrading to 1.1.1 did not solve my issue.
-Original Message-
From: Brandon Williams [mailto:dri...@gmail.com]
Sent: Monday, June 04, 2012 11:24 PM
To: user@cassandra.apache.org
Subject: Re: memory issue on 1.1.0
Perhaps
, validation_class:CounterColumnType)],
default_validation_class:CounterColumnType, caching:keys_only)
])
-Original Message-
From: Poziombka, Wade L [mailto:wade.l.poziom...@intel.com]
Sent: Tuesday, June 05, 2012 3:09 PM
To: user@cassandra.apache.org
Subject: RE: memory issue
Just to check, do you have JNA setup correctly? (You should see a couple of
log messages about it shortly after startup.) Truncate also performs a
snapshot by default.
On Wed, Jun 6, 2012 at 12:38 PM, Poziombka, Wade L
wade.l.poziom...@intel.com wrote:
**
However, after all the work I
I believe so. There are no warnings on startup.
So is there a preferred way to completely eliminate a column family?
From: Tyler Hobbs [mailto:ty...@datastax.com]
Sent: Wednesday, June 06, 2012 1:17 PM
To: user@cassandra.apache.org
Subject: Re: memory issue on 1.1.0
Just to check, do you have
eliminate a column family?
From: Tyler Hobbs [mailto:ty...@datastax.com]
Sent: Wednesday, June 06, 2012 1:17 PM
To: user@cassandra.apache.org
Subject: Re: memory issue on 1.1.0
Just to check, do you have JNA setup correctly? (You should see a couple of
log messages about it shortly after
Alas, upgrading to 1.1.1 did not solve my issue.
-Original Message-
From: Brandon Williams [mailto:dri...@gmail.com]
Sent: Monday, June 04, 2012 11:24 PM
To: user@cassandra.apache.org
Subject: Re: memory issue on 1.1.0
Perhaps the deletes: https://issues.apache.org/jira/browse/CASSANDRA
, Wade L wrote:
Alas, upgrading to 1.1.1 did not solve my issue.
-Original Message-
From: Brandon Williams [mailto:dri...@gmail.com]
Sent: Monday, June 04, 2012 11:24 PM
To: user@cassandra.apache.org
Subject: Re: memory issue on 1.1.0
Perhaps the deletes: https://issues.apache.org
, June 05, 2012 2:24 PM
To: user@cassandra.apache.org
Subject: Re: memory issue on 1.1.0
Hi Wade
I don't know if your scenario matches mine, but I've been struggling with
memory pressure in 1.x as well. I made the jump from 0.7.9 to 1.1.0, along
with enabling compression and levelled compactions
, 2012 3:09 PM
To: user@cassandra.apache.org
Subject: RE: memory issue on 1.1.0
Thank you. I do have some of the same observations. Do you do deletes?
My observation is that without deletes (or column updates I guess) I can run
forever happy. but when I run (what for me is a batch process
Had a look at the log, this message
INFO [ScheduledTasks:1] 2012-06-03 17:49:01,559 StorageService.java (line
2772) Unable to reduce heap usage since there are no dirty column families
appears correct, it happens after some flush activity and there are not CF's
with memtable data. But the
and applying the mutations. Mutations are completing
at about 20,000/minute roughly.
From: aaron morton [mailto:aa...@thelastpickle.com]
Sent: Monday, June 04, 2012 4:17 PM
To: user@cassandra.apache.org
Subject: Re: memory issue on 1.1.0
Had a look at the log, this message
INFO [ScheduledTasks
Sent: Monday, June 04, 2012 7:23 PM
To: user@cassandra.apache.org
Subject: RE: memory issue on 1.1.0
What JVM settings do you have?
-Xms8G
-Xmx8G
-Xmn800m
-XX:+HeapDumpOnOutOfMemoryError
-XX:+UseParNewGC
-XX:+UseConcMarkSweepGC
-XX
Perhaps the deletes: https://issues.apache.org/jira/browse/CASSANDRA-3741
-Brandon
On Sun, Jun 3, 2012 at 6:12 PM, Poziombka, Wade L
wade.l.poziom...@intel.com wrote:
Running a very write intensive (new column, delete old column etc.) process
and failing on memory. Log file attached.
20 matches
Mail list logo
