Re: Cassandra 3.11.4 Node the load starts to increase after few minutes to 40 on 4 CPU machine

Hi Reid, Thank you for your extensive response. I don't think that we have such a person and in any case, even if I am a Software Engineer I would be curious to deep dive into the problem and understand the reason. The only observation that I have right now is that I have in the same cluster 2 key

***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: Cassandra 4 alpha/alpha2

A new thing like this would be much better served by the community through several iterations. For instance, over the last year I've developed a tool for spinning up lab clusters, it's here: https://thelastpickle.com/tlp-cluster/ I had to make a *lot* of tradeoffs here. Everything Jeff mentioned

Memory Recommendations for G1GC

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 that needs to be allocated to heap space when using G1GC? For GC, we currently use CMS. Along with the version upgrade, we'll be running the stateful

Re: oversized partition detection ? monitoring the partitions growth ?

You can set compaction_large_partition_warning_threshold_mb and alert on logs . Writing large partition {}/{}:{} ({}) to sstable {} Chri

Re: Cassandra 4 alpha/alpha2

Lots of this, but also getting into the weeds, it's pretty clear this is nontrivial: - If we did an AWS AMI, would we also do Azure? GCP? AliCloud? OCI? Where do we stop? - What if there's a security hole in the base image - who's responsible for fixing that? We could have tooling that makes a new

Re: Cassandra 4 alpha/alpha2

That is indeed what Amazon AMIs are for. 😊 However if your question is “why don’t the C* developers do that for people?” the answer is going to be some mix of “people only do so much work for free” and “the ones that don’t do it for free have a company you pay to do things like that (Datastax)

Re: Cassandra 3.11.4 Node the load starts to increase after few minutes to 40 on 4 CPU machine

Hi Sergio, I’m definitely not enough of a network wonk to make definitive statements on network configuration, finding your in-company network expert is definitely going to be a lot more productive. I’ve forgotten if you are on-prem or in AWS, so if in AWS replace “your network wonk” with “you