You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (Commented) (JIRA)" <ji...@apache.org> on 2011/10/13 21:27:11 UTC
[jira] [Commented] (CASSANDRA-3124) java heap limit for nodetool
[ https://issues.apache.org/jira/browse/CASSANDRA-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13126835#comment-13126835 ]
Jonathan Ellis commented on CASSANDRA-3124:
-------------------------------------------
I don't think nodetool should ever need more than 32M, so that's reasonable.
Committed in r1183046.
> java heap limit for nodetool
> ----------------------------
>
> Key: CASSANDRA-3124
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3124
> Project: Cassandra
> Issue Type: Improvement
> Components: Core, Tools
> Affects Versions: 0.8.1, 0.8.2, 0.8.3, 0.8.4
> Environment: not important
> Reporter: Zenek Kraweznik
> Priority: Minor
>
> by defaull (from debian package)
> # nodetool
> Error occurred during initialization of VM
> Could not reserve enough space for object heap
> Could not create the Java virtual machine.
> #
> and:
> --- /usr/bin/nodetool.old 2011-09-02 14:15:14.228152799 +0200
> +++ /usr/bin/nodetool 2011-09-02 14:14:28.745154552 +0200
> @@ -55,7 +55,7 @@
> ;;
> esac
> -$JAVA -cp $CLASSPATH -Dstorage-config=$CASSANDRA_CONF \
> +$JAVA -Xmx32m -cp $CLASSPATH -Dstorage-config=$CASSANDRA_CONF \
> -Dlog4j.configuration=log4j-tools.properties \
> org.apache.cassandra.tools.NodeCmd $@
> after every upgrade i had to add limit manually. I think it's good idea to add it by default ;)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira