cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Jirsa (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-12739) Nodetool uses cassandra-env.sh MAX_HEAP_SIZE if set
Date Sat, 03 Dec 2016 06:39:58 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-12739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jeff Jirsa updated CASSANDRA-12739:
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 3.10
                   3.0.11
    Reproduced In: 3.0.5, 2.2.6  (was: 2.2.6, 3.0.5)
           Status: Resolved  (was: Ready to Commit)

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)

Mime
View raw message