Re: Memory and caches

Hello Bowen, Jon, Thank you for your answers. I will continue investigating following your advice, currently there is no performance issue, and we have good HW etc, so probably no need to optimize caches. Have a good day, Sébastien. Le lun. 27 nov. 2023 à 20:00, Jon Haddad a écrit : > I haven

Re: Memory and caches

I haven't found chunk cache to be particularly useful. It's a fairly small cache that could only help when you're dealing with a small hot dataset. I wouldn't bother increasing memory for it. Key cache can be helpful, but it depends on the workload. I generally recommend optimizing for your

Re: Memory and caches

Hi Sebastien, What's your goal? Improving cache hit rate purely for the sake of having a higher hit rate is rarely a good goal, because higher cache hit rate doesn't always mean faster operations. Do you have specific issues with performance? If so, can you please tell us more about it? Thi

Re: Memory requirements for Cassandra reaper

Thanks a lot. On Tue, 4 May 2021 at 19:51, Erick Ramirez wrote: > 2GB is allocated to the Reaper JVM on startup (see > https://github.com/thelastpickle/cassandra-reaper/blob/2.2.4/src/packaging/bin/cassandra-reaper#L90-L91 > ). > > If you just want to test it out on a machine with only 8GB, you

Re: Memory requirements for Cassandra reaper

2GB is allocated to the Reaper JVM on startup (see https://github.com/thelastpickle/cassandra-reaper/blob/2.2.4/src/packaging/bin/cassandra-reaper#L90-L91 ). If you just want to test it out on a machine with only 8GB, you can update the cassandra-reaper script to only use 1GB by setting -Xms1G and

Re: Memory requirements for Cassandra reaper

Hi Surbhi, I don't know the memory requirements, but speaking from my observation, a single Cassandra Reaper instance with an external postgres database storage backend, and managing a single small Cassandra cluster, the Cassandra Reaper's Java process memory usage is slightly short of 1GB.

Re: Memory Map settings for Cassandra

Thank you On Thu, Apr 15, 2021 at 7:20 PM Kane Wilson wrote: > Yes that warning will still appear because it's a startup check and > doesn't take into account the disk_access_mode setting. > > You may be able to cope with just indexes. Note this is still not an ideal > solution as you won't be m

Re: Memory Map settings for Cassandra

Yes that warning will still appear because it's a startup check and doesn't take into account the disk_access_mode setting. You may be able to cope with just indexes. Note this is still not an ideal solution as you won't be making full use of your available memory. raft.so - Cassandra consulting,

Re: Memory Map settings for Cassandra

Also, I just restarted my Cassandra process by setting "disk_access_mode: mmap_index_only" and I still see the same WARN message, I believe it's just a startup check and doesn't rely on the disk_access_mode value WARN [main] 2021-04-16 00:08:00,088 StartupChecks.java:311 - Maximum > number of m

Re: Memory Map settings for Cassandra

Thank you Kane and Jeff. can I survive with a low mmap value of 65530 with "disk_acces_mode = mmap_index_only" ? does this hold true even for higher workloads with larger datasets like ~1TB per node? On Thu, Apr 15, 2021 at 4:43 PM Jeff Jirsa wrote: > disk_acces_mode = mmap_index_only to use fe

Re: Memory Map settings for Cassandra

disk_acces_mode = mmap_index_only to use fewer maps (or disable it entirely as appropriate). On Thu, Apr 15, 2021 at 4:42 PM Kane Wilson wrote: > Cassandra mmaps SSTables into memory, of which there can be many files > (including all their indexes and what not). Typically it'll do so greedily

Re: Memory Map settings for Cassandra

Cassandra mmaps SSTables into memory, of which there can be many files (including all their indexes and what not). Typically it'll do so greedily until you run out of RAM. 65k map areas tends to be quite low and can easily be exceeded - you'd likely need very low density nodes to avoid going over 6

Re: Memory decline

Hi jeff, Provided information below. How can i check how much memory allocated to direct memory for jvm On Thu, Jun 18, 2020 at 11:38 AM Jeff Jirsa wrote: > Some things that are helpful: > > - What version of Cassandra > 3.11.3 > - How much memory allocated to heap > Max_heap_size 8G Heap_new_

Re: Memory decline

Some things that are helpful: - What version of Cassandra - How much memory allocated to heap - How much memory allocated to direct memory for the JVM - How much memory on the full system - Do you have a heap dump? - Do you have a heap histogram? - How much data on disk? - What are your compressio

Re: Memory decline

Just to confirm, is this memory decline outside of the Cassandra process? If so, I’d look at crond and at memory held for network traffic. Those are the two areas I’ve seen leak. If you’ve configured to have swap=0, then you end up in a position where even if the memory usage is stale, nothin

Re: Memory usage more than heap memory

It doesn't sound like you've had a good read of Michael Shuler's responses. TL;DR it's not a Cassandra issue, it's a reporting issue. I recommend you go and read Michael's response. Cheers! >

Re: Memory usage more than heap memory

Thanks all for the help. But I am bit lost though because in my case top command is showing that Cassandra process is consuming 18G (heap+nonheap + pagecache) Free command is showing 12G as available out of 24G total. Now my heap is 8G and off heap metrics show 1.6G ( using jmxterm) usage. So my u

Re: Memory usage more than heap memory

> > I observe long running nodes have high non heap memory footprint then a > recently started node. That is the reason I am interested in find non heap > memory usage by Cassandra node. What could be the reason of high non heap > memory footprint in long running cluster? > Memory utilisation grow

Re: Memory usage more than heap memory

I observe long running nodes have high non heap memory footprint then a recently started node. That is the reason I am interested in find non heap memory usage by Cassandra node. What could be the reason of high non heap memory footprint in long running cluster? Regards Himanshu On Sat, Apr 11,

Re: Memory usage more than heap memory

Hi Himanshu, On Sat, Apr 11, 2020 at 8:47 PM HImanshu Sharma wrote: > I am not worried about page cache. I want to monitor memory pressure, I want > to check that if heap+non heap usage goes above certain level then I can take > certain action. But due to this page cache thing, I am not sure ho

Re: Memory usage more than heap memory

Nodetool isn't really meant for monitoring usage. There are a number of existing tools to grab and track jvm heap usage. Enable JMX and pull the info into something custom, or using a grafana template, for instance, which usually uses JMX internally. ie. this one graphs heap usage historicall

Re: Memory usage more than heap memory

For some simple and helpful explanations of the behavior you are observing, some ideas on what to look for in monitoring, as well as some interesting experiments on the "play" page (last link), have a look at https://www.linuxatemyram.com/ - this is general linux memory behavior and not unique

Re: Memory usage more than heap memory

Hi I am not worried about page cache. I want to monitor memory pressure, I want to check that if heap+non heap usage goes above certain level then I can take certain action. But due to this page cache thing, I am not sure how to find actual memory usage( heap and off heap). Heap will not be more t

Re: Memory usage more than heap memory

One more point, if you are worried about high memory usage then read about disk_access_mode configuration of Cassandra. By default it will cause high memory usage. Setting it to mmap_index_only can help. On Sat, Apr 11, 2020 at 5:43 PM Laxmikant Upadhyay wrote: > Hi, > > You can read section '

Re: Memory usage more than heap memory

Hi, You can read section 'OS Page Cache Usage' on http://cassandra.apache.org/doc/latest/troubleshooting/use_tools.html Also, don't worry about memory usage (page cache) not decreasing even if no traffic ...it will come down when required (for example: a new application needs it when boot up). On

Re: Memory usage more than heap memory

Hi I am observing memory usage in top command, but there in RSS it is showing 18G ( which I think is sum of used memo + page cache). I want to know how to find how much used by Cassandra process and how much of it is in page cache. I want this information because I want to check memory usage for m

Re: Memory usage more than heap memory

You can look at top command. There is column of memory Regards, Nitan Cell: 510 449 9629 > On Apr 11, 2020, at 11:10 AM, HImanshu Sharma > wrote: > >  > Hi > > But I see memory not decreasing even if there is no traffic on cluster. How > can I find actual memory usage by Cassandra process

Re: Memory usage more than heap memory

Hi But I see memory not decreasing even if there is no traffic on cluster. How can I find actual memory usage by Cassandra process. If it is OS page cache then how to find how much is page cache and how much is used by process? Thanks Himanshu On Sat, Apr 11, 2020 at 9:07 PM Laxmikant Upadhya

Re: Memory usage more than heap memory

It is OS page cache used during read..your os will leverage memory if not being used by any other applications and it improves your read performance. On Sat, Apr 11, 2020, 12:47 PM HImanshu Sharma wrote: > Hi > > I am very new to the use of cassandra. In a cassandra cluster of 3 nodes, > I am ob

Re: ***UNCHECKED*** Re: Memory Recommendations for G1GC

ive stalls happening on either reading > from disk or flushing dirty pages to disk. > > > > > > *From: *Ben Mills > *Reply-To: *"user@cassandra.apache.org" > *Date: *Monday, November 4, 2019 at 12:14 PM > *To: *"user@cassandra.apache.org" > *Subject: *Re: ***UNCHECKED*** Re: Memory Recommendations for G1GC > > > > CGroup >

Re: ***UNCHECKED*** Re: Memory Recommendations for G1GC

To: "user@cassandra.apache.org" Subject: Re: ***UNCHECKED*** Re: Memory Recommendations for G1GC CGroup

Re: ***UNCHECKED*** Re: Memory Recommendations for G1GC

t; > > > *From: *Ben Mills > *Reply-To: *"user@cassandra.apache.org" > *Date: *Monday, November 4, 2019 at 8:51 AM > *To: *"user@cassandra.apache.org" > *Subject: *Re: ***UNCHECKED*** Re: Memory Recommendations for G1GC > > > > *Message from External Se

Re: ***UNCHECKED*** Re: Memory Recommendations for G1GC

: "user@cassandra.apache.org" Date: Monday, November 4, 2019 at 8:51 AM To: "user@cassandra.apache.org" Subject: Re: ***UNCHECKED*** Re: Memory Recommendations for G1GC Message from External Sender Hi (yet again) Sergio, Finally, note that we use this sidecar<https://urldefens

Re: ***UNCHECKED*** Re: Memory Recommendations for G1GC

Hi (yet again) Sergio, Finally, note that we use this sidecar for shipping metrics to Stackdriver. It runs as a second container within our Prometheus stateful set. On Mon, Nov 4, 2019 at 8:46 AM Ben Mills wrote: > Hi (again) Serg

Re: ***UNCHECKED*** Re: Memory Recommendations for G1GC

Hi (again) Sergio, I forgot to note that along with Prometheus, we use Grafana (with Prometheus as its data source) as well as Stackdriver for monitoring. As Stackdriver is still developing (i.e. does not have all the features we need), we tend to use it for the basics (i.e. monitoring and alerti

Re: ***UNCHECKED*** Re: Memory Recommendations for G1GC

Hi Sergio, Thanks for this and sorry for the slow reply. We are indeed still running Java 8 and so it's very helpful. This Cassandra cluster has been running reliably in Kubernetes for several years, and while we've had some repair-related issues, they are not related to container orchestration

***UNCHECKED*** Re: Memory Recommendations for G1GC

Hi Ben, Well, I had a similar question and Jon Haddad was preferring ParNew + CMS over G1GC for java 8. https://lists.apache.org/thread.html/283547619b1dcdcddb80947a45e2178158394e317f3092b8959ba879@%3Cuser.cassandra.apache.org%3E It depends on your JVM and in any case, I would test it based on you

Re: Memory Recommendations for G1GC

Thanks Sergio - that's good advice and we have this built into the plan. Have you heard a solid/consistent recommendation/requirement as to the amount of memory heap requires for G1GC? On Fri, Nov 1, 2019 at 5:11 PM Sergio wrote: > In any case I would test with tlp-stress or Cassandra stress too

Re: Memory Recommendations for G1GC

Thanks Reid, We currently only have ~1GB data per node with a replication factor of 3. The amount of data will certainly grow, though I have no solid projections at this time. The current memory and CPU resources are quite low (for Cassandra) and so along with the upgrade we plan to increase both.

Re: Memory Recommendations for G1GC

In any case I would test with tlp-stress or Cassandra stress tool any configuration Sergio On Fri, Nov 1, 2019, 12:31 PM Ben Mills wrote: > Greetings, > > We are planning a Cassandra upgrade from 3.7 to 3.11.5 and considering a > change to the GC config. > > What is the minimum amount of memory

Re: Memory Recommendations for G1GC

Maybe I’m missing something. You’re expecting less than 1 gig of data per node? Unless this is some situation of super-high data churn/brief TTL, it sounds like you’ll end up with your entire database in memory. From: Ben Mills Reply-To: "user@cassandra.apache.org" Date: Friday, November 1,

Re: [Marketing Mail] Re: Memory leak and lockup on our 2.2.7 Cassandra cluster.

In the future you may find SASI indexes useful for indexing Cassandra data. Shameless blog post plug: http://rustyrazorblade.com/2016/02/cassandra-secondary-index-preview-1/ Deep technical dive: http://www.doanduyhai.com/blog/?p=2058 On Thu, Aug 4, 2016 at 11:45 AM Kevin Burton wrote: > BTW. we

Re: [Marketing Mail] Re: Memory leak and lockup on our 2.2.7 Cassandra cluster.

BTW. we think we tracked this down to using large partitions to implement inverted indexes. C* just doesn't do a reasonable job at all with large partitions so we're going to migrate this use case to using Elasticsearch On Wed, Aug 3, 2016 at 1:54 PM, Ben Slater wrote: > Yep, that was what I w

Re: [Marketing Mail] Re: Memory leak and lockup on our 2.2.7 Cassandra cluster.

Yep, that was what I was referring to. On Thu, 4 Aug 2016 2:24 am Reynald Bourtembourg < reynald.bourtembo...@esrf.fr> wrote: > Hi, > > Maybe Ben was referring to this issue which has been mentioned recently on > this mailing list: > https://issues.apache.org/jira/browse/CASSANDRA-11887 > > Chee

Re: [Marketing Mail] Re: Memory leak and lockup on our 2.2.7 Cassandra cluster.

Have you tried using the G1 garbage collector instead of CMS? We had the same issues that things were normally fine, but as soon as something extraordinary happened, a node could go into GC hell and never recover, and that could then spread to other nodes as they took up the slack, trapping them i

Re: [Marketing Mail] Re: Memory leak and lockup on our 2.2.7 Cassandra cluster.

We usually use 100 per every 5 minutes.. but you're right. We might actually move this use case over to using Elasticsearch in the next couple of weeks. On Wed, Aug 3, 2016 at 11:09 AM, Jonathan Haddad wrote: > Kevin, > > "Our scheme uses large buckets of content where we write to a > bucket/pa

Re: [Marketing Mail] Re: Memory leak and lockup on our 2.2.7 Cassandra cluster.

Kevin, "Our scheme uses large buckets of content where we write to a bucket/partition for 5 minutes, then move to a new one." Are you writing to a single partition and only that partition for 5 minutes? If so, you should really rethink your data model. This method does not scale as you add node

Re: [Marketing Mail] Re: Memory leak and lockup on our 2.2.7 Cassandra cluster.

Hi, Maybe Ben was referring to this issue which has been mentioned recently on this mailing list: https://issues.apache.org/jira/browse/CASSANDRA-11887 Cheers, Reynald On 03/08/2016 18:09, Romain Hardouin wrote: >Curious why the 2.2 to 3.x upgrade path is risky at best. I guess that upgrade

Re: Memory leak and lockup on our 2.2.7 Cassandra cluster.

> Curious why the 2.2 to 3.x upgrade path is risky at best. I guess that >upgrade from 2.2 is less tested by DataStax QA because DSE4 used C* 2.1, not >2.2.I would say the safest upgrade is 2.1 to 3.0.x Best, Romain

Re: Memory leak and lockup on our 2.2.7 Cassandra cluster.

DuyHai. Yes. We're generally happy with our disk throughput. We're on all SSD and have about 60 boxes. The amount of data written isn't THAT much. Maybe 5GB max... but its over 60 boxes. On Wed, Aug 3, 2016 at 3:49 AM, DuyHai Doan wrote: > On a side node, do you monitor your disk I/O to s

Re: Memory leak and lockup on our 2.2.7 Cassandra cluster.

Curious why the 2.2 to 3.x upgrade path is risky at best. Do you mean that this is just for OUR use case since we're having some issues or that the upgrade path is risky in general? On Wed, Aug 3, 2016 at 3:41 AM, Ben Slater wrote: > Yes, looks like you have a (at least one) 100MB partition whic

Re: Memory leak and lockup on our 2.2.7 Cassandra cluster.

On a side node, do you monitor your disk I/O to see whether the disk bandwidth can catch up with the huge spikes in write ? Use dstat during the insert storm to see if you have big values for CPU wait On Wed, Aug 3, 2016 at 12:41 PM, Ben Slater wrote: > Yes, looks like you have a (at least one)

Re: Memory leak and lockup on our 2.2.7 Cassandra cluster.

Yes, looks like you have a (at least one) 100MB partition which is big enough to cause issues. When you do lots of writes to the large partition it is likely to end up getting compacted (as per the log) and compactions often use a lot of memory / cause a lot of GC when they hit large partitions. Th

Re: Memory leak and lockup on our 2.2.7 Cassandra cluster.

I have a theory as to what I think is happening here. There is a correlation between the massive content all at once, and our outags. Our scheme uses large buckets of content where we write to a bucket/partition for 5 minutes, then move to a new one. This way we can page through buckets. I thin

Re: memory usage problem of Metadata.tokenMap.tokenToHost

There are still a couple of tickets being worked on for 2.1.10 and the release will come afterwards. You can check the list: https://datastax-oss.atlassian.net/browse/JAVA-989?jql=project%20%3D%20JAVA%20AND%20fixVersion%20%3D%202.1.10 On Mon, Jan 4, 2016 at 5:57 AM, joseph gao wrote: > By the wa

Re: memory usage problem of Metadata.tokenMap.tokenToHost

By the way, when would be the version 2.1.10 published? 2015-12-15 10:02 GMT+08:00 joseph gao : > That's great. Thanks, Alex! > > 2015-10-02 0:36 GMT+08:00 Alexandre Dutra : > >> I confirm that the optional schema metadata feature (JAVA-828 >> )

Re: memory usage problem of Metadata.tokenMap.tokenToHost

That's great. Thanks, Alex! 2015-10-02 0:36 GMT+08:00 Alexandre Dutra : > I confirm that the optional schema metadata feature (JAVA-828 > ) has been merged > upstream and is included in driver 3.0.0-alpha3 and will as well be > included in the f

Re: memory usage problem of Metadata.tokenMap.tokenToHost

I confirm that the optional schema metadata feature (JAVA-828 ) has been merged upstream and is included in driver 3.0.0-alpha3 and will as well be included in the forthcoming 2.1.8 version. On a side note, JAVA-664

Re: memory usage problem of Metadata.tokenMap.tokenToHost

Besides the others' advice that 2000+ keyspaces might be too much, the latest Java driver (2.0.11) includes an option to disable the Metadata API http://www.datastax.com/dev/blog/datastax-java-driver-2-0-11-released. I'm not sure at this moment if this has been merged into 2.1 already. On Sun, Sep

Re: memory usage problem of Metadata.tokenMap.tokenToHost

On Sun, Sep 20, 2015 at 9:22 AM, joseph gao wrote: >My application uses 2000+ keyspaces, and will dynamically create > keyspaces and tables. > While I agree with your observation (and think you should file a ticket at issues.apache.org and let the list know the URL) that there is low hanging

Re: memory usage problem of Metadata.tokenMap.tokenToHost

In practice there are not many good reasons to use that many keyspaces and tables. If the use case is multi tenancy then you’re almost always better off just using a combination of version tables and tenantId to give you flexibility as well as separation of client data. If you have that many dat

Re: memory usage problem of Metadata.tokenMap.tokenToHost

Hi Joseph, I think 2000 keyspaces might be just too much. Fewer keyspaces (and CFs) will probably work much better. kind regards, Christian On Tue, Sep 22, 2015 at 9:29 AM, joseph gao wrote: > Hi, anybody could help me? > > 2015-09-21 0:47 GMT+08:00 joseph gao : > >> ps : that's the code in j

Re: memory usage problem of Metadata.tokenMap.tokenToHost

Hi, anybody could help me? 2015-09-21 0:47 GMT+08:00 joseph gao : > ps : that's the code in java drive , in MetaData.TokenMap.build: > > for (KeyspaceMetadata keyspace : keyspaces) > { > ReplicationStrategy strategy = keyspace.replicationStrategy(); > Map> ksTokens = (strategy == null) >

Re: memory usage problem of Metadata.tokenMap.tokenToHost

ps : that's the code in java drive , in MetaData.TokenMap.build: for (KeyspaceMetadata keyspace : keyspaces) { ReplicationStrategy strategy = keyspace.replicationStrategy(); Map> ksTokens = (strategy == null) ? makeNonReplicatedMap(tokenToPrimary) : strategy.computeTokenToR

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 result in part of

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 o

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 > Objet : Memory is

RE: Memory issue

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 a écrit sur 21/05/2014 06:59:05 : > De : opensaf dev > A : u

Re: memory usage spikes

tion/cassandra/2.0/mobile/cassandra/install/installJnaRHEL.html? >> >> >> >> Don >> >> >> >> *From:* prem yadav [mailto:ipremya...@gmail.com] >> *Sent:* Wednesday, March 26, 2014 10:36 AM >> *To:* user@cassandra.apache.org >> *Subject:

Re: memory usage spikes

; http://www.datastax.com/documentation/cassandra/2.0/mobile/cassandra/install/installJnaRHEL.html? > > > > Don > > > > *From:* prem yadav [mailto:ipremya...@gmail.com] > *Sent:* Wednesday, March 26, 2014 10:36 AM > *To:* user@cassandra.apache.org > *Subject:* Re: memory

RE: memory usage spikes

/cassandra/install/installJnaRHEL.html ? Don From: prem yadav [mailto:ipremya...@gmail.com] Sent: Wednesday, March 26, 2014 10:36 AM To: user@cassandra.apache.org Subject: Re: memory usage spikes here: ps -p `/usr/java/jdk1.6.0_37/bin/jps | awk '/Dse/ {print $1}'` uww SER PID

Re: memory usage spikes

here: ps -p `/usr/java/jdk1.6.0_37/bin/jps | awk '/Dse/ {print $1}'` uww SER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND 497 20450 0.9 31.0 4727620 2502644 ? SLl 06:55 3:28 /usr/java/jdk1.6.0_37//bin/java -ea -javaagent:/usr/share/dse/cassandra/lib/jamm-0.2.5.

Re: memory usage spikes

Hi, RSS or VIRT? Could you paste output of: $ ps -p `jps | awk '/CassandraDaemon/ {print $1}'` uww please? On Wed, Mar 26, 2014 at 5:20 PM, prem yadav wrote: > Hi, > in another thread, I has mentioned that we had issue with Cassandra > getting killed by kernel due to OOM. Downgrading to jdk6_

Re: Memory Manager

Without knowing what the schema is and what the load is or anything about the workload I would suggest: Using 4G for the heap and 800 MB for the new heap. The 128 MB setting you have is way too small. If you are running our of heap space the simple thing is to add more. Using the default GC s

Re: Memory Manager

Yes, I already have do it, but in my application, my configuration is needed. But the problem was solved. The problem was a leak of memory in my code. Thanks. 2012/11/14 aaron morton > Have you tried using the defaults in cassandra-env.sh ? Your setting are > very different. > > > https://gith

Re: Memory Manager

Have you tried using the defaults in cassandra-env.sh ? Your setting are very different. https://github.com/apache/cassandra/blob/cassandra-1.1/conf/cassandra-env.sh Cheers - Aaron Morton Freelance Developer @aaronmorton http://www.thelastpickle.com On 13/11/2012, at 11:35 P

Re: Memory Manager

-Xmx2G -Xms512M -Xmn128M -Djava.net.preferIPv4Stack=true -Djava.rmi.server.hostname=10.10.0.211 -Dcom.sun.management.jmxremote.port=7199 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -XX:+UseConcMarkSweepGC -XX:ParallelCMSThreads=4 -XX:+CMSIncrementalMod

Re: Memory Manager

Can you supply your java parameters? On Mon, Nov 12, 2012 at 7:29 AM, Everton Lima wrote: > Hi people, > > I was using cassandra on distributed project. I am using java 6 and > cassandra 1.1.6. My problem is in Memory manager (I think). My system was > throwing heap limit exception. > The problem

Re: Memory Usage of a connection

On Fri, Aug 31, 2012 at 11:27 AM, Peter Schuller < peter.schul...@infidyne.com> wrote: > > Could these 500 connections/second cause (on average) 2600Mb memory usage > > per 2 second ~ 1300Mb/second. > > or For 1 connection around 2-3Mb. > > In terms of garbage generated it's much less about number

Re: Memory Usage of a connection

> Could these 500 connections/second cause (on average) 2600Mb memory usage > per 2 second ~ 1300Mb/second. > or For 1 connection around 2-3Mb. In terms of garbage generated it's much less about number of connections as it is about what you're doing with them. Are you for example requesting large

Re: Memory Usage of a connection

PS: everything above is in bytes, not bits. On Fri, Aug 31, 2012 at 11:03 AM, rohit bhatia wrote: > I was wondering how much would be the memory usage of an established > connection in cassandra's heap space. > > We are noticing extremely frequent young generation garbage collections > (3.2gb yo

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

Re: memory estimate for each key in the key cache

If you get the sizing wrong there area couple of emergency pressure valves in the config… https://github.com/apache/cassandra/blob/trunk/conf/cassandra.yaml#L113 Watch for log messages with "Cassandra is now reducing cache sizes to free up memory." in them. Cheers - Aaron Mort

Re: memory estimate for each key in the key cache

> It is not telling you to multiply your key size by 10-12, it is telling you to > multiply the output of the nodetool cfstats reported "key cache size" by > 10-12. The  "key cache size" reported is actually the number of keys in the key cache. So, it is the same thing as suggesting each key ta

  1   2   >