Re: Is it a memory issue?

Compaction cargts > eventdata.eventdata_event_time_idx 32098562606 42616107664 bytes > 75.32% > Active compaction remaining time : 0h11m12s > > > *From:* Ben Slater > *Date:* 2016-11-07 11:41 > *To:* user > *Subject:* Re: Is it a memory issue? >

Re: Is it a memory issue?

memory issue? This sounds to me like your writes go ahead of compactions trying to keep up which can eventually cause issues. Keep an eye on nodetool compactionstats if the number of compactions continually climbs then you are writing faster than Cassandra can actually process. If this is

Re: Is it a memory issue?

This sounds to me like your writes go ahead of compactions trying to keep up which can eventually cause issues. Keep an eye on nodetool compactionstats if the number of compactions continually climbs then you are writing faster than Cassandra can actually process. If this is happening then you need

Is it a memory issue?

Hi All, We have one issue on C* testing. At first the inserting was very fast and TPS was about 30K/s, but when the size of data rows reached 2 billion, the insertion rate decreased very badly and the TPS was 20K/s. When the size of rows reached 2.3 billion, the TPS decreased to 0.5K/s, and writ

Re: Memory issue

> 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 re

Re: Memory issue

On Fri, May 23, 2014 at 2:08 PM, opensaf dev 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/C

Re: Memory issue

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 wrote: > > On Wed, May 21, 2014 at 12:59 AM, opensaf dev wrote: > >> When I run as user cassandra, it starts and runs fine. > > > Why do you want to

Re: Memory issue

On Wed, May 21, 2014 at 12:59 AM, opensaf dev 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

Re: Memory issue

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

RE: Memory issue

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 a écrit sur 21/05/2014 06:59:05 : > De : opensaf dev > A : user@cassandra.apache.org, > Date : 21/05/2014 07:00 > Ob

RE: Memory issue

> 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

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 [m

Re: memory issue on 1.1.0

ompletely 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 coup

RE: memory issue on 1.1.0

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

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 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

Re: memory issue on 1.1.0

ssage- > 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 on 1.1.0 > > Thank you. I do have some of the same observations. Do you do deletes? > > My observation is that

Re: memory issue on 1.1.0

t; 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 t

RE: memory issue on 1.1.0

ne 05, 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 pr

RE: memory issue on 1.1.0

, 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 c

Re: memory issue on 1.1.0

heap usage, instability and high latency. On 2012-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@c

RE: memory issue on 1.1.0

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

RE: memory issue on 1.1.0

Thanks for this pointer I will retest with 1.1.1, which seems to be when this is fixed. -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

Re: memory issue on 1.1.0

Perhaps the deletes: https://issues.apache.org/jira/browse/CASSANDRA-3741 -Brandon On Sun, Jun 3, 2012 at 6:12 PM, Poziombka, Wade L wrote: > Running a very write intensive (new column, delete old column etc.) process > and failing on memory.  Log file attached. > > Curiously when I add new dat

RE: memory issue on 1.1.0

ade L 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

RE: memory issue on 1.1.0

ading from this queue 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, thi

Re: memory issue on 1.1.0

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 h