Re: optimization to cassandra-env.sh

[R1 J1]

Thank  you Sean and Rahul for the consult

On Sun, Jul 29, 2018 at 6:52 PM, Rahul Singh 
wrote:

> Depends on which GC you are using but you can definitely manage GC - but
> you will always be stuck to the upper limit of memory.
>
> I found the Hubspot gc visualizer and the associated blog post very
> helpful in the past.
>
> *https://github.com/HubSpot/gc_log_visualizer/blob/master/README.md*
> 
>
>
>
> *https://product.hubspot.com/blog/g1gc-fundamentals-lessons-from-taming-garbage-collection*
> 
>
> Rahul
> On Jul 26, 2018, 1:27 PM -0400, R1 J1 , wrote:
>
> 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
>
>

Re: optimization to cassandra-env.sh

[Rahul Singh]

Depends on which GC you are using but you can definitely manage GC - but you 
will always be stuck to the upper limit of memory.

I found the Hubspot gc visualizer and the associated blog post very helpful in 
the past.

https://github.com/HubSpot/gc_log_visualizer/blob/master/README.md


https://product.hubspot.com/blog/g1gc-fundamentals-lessons-from-taming-garbage-collection

Rahul
On Jul 26, 2018, 1:27 PM -0400, R1 J1 , wrote:
> 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
>

RE: [EXTERNAL] optimization to cassandra-env.sh

[Durity, Sean R]

This is a very good explanation of CMS tuning for Cassandra:
http://thelastpickle.com/blog/2018/04/11/gc-tuning.html
(author Jon Haddad has extensive Cassandra experience – a super star in our 
field)

Sean Durity
From: Durity, Sean R 
Sent: Thursday, July 26, 2018 2:08 PM
To: user@cassandra.apache.org
Subject: RE: [EXTERNAL] optimization to cassandra-env.sh

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 mailto:rjsoft...@gmail.com>>
Sent: Thursday, July 26, 2018 1:28 PM
To: user@cassandra.apache.org<mailto: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.



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.

RE: [EXTERNAL] optimization to cassandra-env.sh

[Durity, Sean R]

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

optimization to cassandra-env.sh

[R1 J1]

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