You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brad Vernon (JIRA)" <ji...@apache.org> on 2016/09/30 21:20:20 UTC
[jira] [Created] (CASSANDRA-12739) Nodetool uses cassandra-env.sh
MAX_HEAP_SIZE if set
Brad Vernon created CASSANDRA-12739:
---------------------------------------
Summary: 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
Attachments: cass-21_tools_xmx.patch, cass-22_tools_xmx.patch, cass-3x_tools_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)