[ https://issues.apache.org/jira/browse/CASSANDRA-12739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15717553#comment-15717553 ]
Jeff Jirsa edited comment on CASSANDRA-12739 at 12/3/16 6:39 AM: ----------------------------------------------------------------- Thanks for the patch [~bvernon] (and for the review, [~eduard.tudenhoefner] ). Committed as {{255505ea7915a1261788018ede37ee8c82ac2062}} was (Author: jjirsa): Thanks for the patch [~bvernon]! Committed as {{255505ea7915a1261788018ede37ee8c82ac2062}} > Nodetool uses cassandra-env.sh MAX_HEAP_SIZE if set > --------------------------------------------------- > > Key: CASSANDRA-12739 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12739 > Project: Cassandra > Issue Type: Bug > Components: Tools > Reporter: Brad Vernon > Fix For: 3.0.11, 3.10 > > Attachments: nodetool_xmx.patch > > > Nodetool and other bash startup scripts load cassandra-env.sh variables > including MAX_HEAP_SIZE as part of CASSANDRA-10679. If cassandra-env.sh has > MAX_HEAP_SIZE set to any value the default heap size needed for the cassandra > tool to run is overridden. > This is a problem if the using a large heap in C* i.e. 16-32G due to each > instance of nodetool or other tool will allocate large heap regardless of > need and could exceed the total RAM available on the system. > Patch removes the check for MAX_HEAP_SIZE being set and uses the default heap > size needed for each tool. -- This message was sent by Atlassian JIRA (v6.3.4#6332)