Check the archives for CMS or G1 (whichever garbage collector you are using). There has been significant and good advice on both. In general, though, G1 has one basic number to set and does very well in our use cases. CMS has lots of black art/science tuning and configuration, but you can test options on a “canary” node and tweak until it runs well.
If you need more help after looking back in the archives, we would need the Cassandra version, JVM type and version, jvm.options (or cassandra-env.sh) and what kinds of errors/gc you are seeing (GC logs can be helpful). Sean Durity From: R1 J1 <rjsoft...@gmail.com> Sent: Thursday, July 26, 2018 1:28 PM To: user@cassandra.apache.org Subject: [EXTERNAL] optimization to cassandra-env.sh Any one has tried to optimize or change cassandra-env.sh in an server installation to make it use more heap size for garbage collection ? Any ideas ? We are having some oom issues and thinking if we have options other than increasing RAM for that node. Regards ________________________________ The information in this Internet Email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this Email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to our clients any opinions or advice contained in this Email are subject to the terms and conditions expressed in any applicable governing The Home Depot terms of business or client engagement letter. The Home Depot disclaims all responsibility and liability for the accuracy and content of this attachment and for any damages or losses arising from any inaccuracies, errors, viruses, e.g., worms, trojan horses, etc., or other items of a destructive nature, which may be contained in this attachment and shall not be liable for direct, indirect, consequential or special damages in connection with this e-mail message or its attachment.
