[CASSANDRA-12739] Nodetool uses cassandra-env.sh MAX_HEAP_SIZE if set

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.0.11, 3.10
• Component/s: Tool/nodetool
• Severity: Normal
• Since Version: 2.1.14
• Assignee: Unassigned
• Reporter: Brad Vernon

Reviewers

Eduard Tudenhoefner

• Created: 30/Sep/16 21:20
• Updated: 16/Apr/19 09:30
• Resolved: 03/Dec/16 06:38

Description

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.