You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Zenek Kraweznik (JIRA)" <ji...@apache.org> on 2011/09/02 14:18:09 UTC
[jira] [Created] (CASSANDRA-3124) java heap limit for nodetool
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.4, 0.8.3, 0.8.2, 0.8.1
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (CASSANDRA-3124) java heap limit for
nodetool
Posted by "Zenek Kraweznik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13101055#comment-13101055 ]
Zenek Kraweznik edited comment on CASSANDRA-3124 at 9/9/11 7:24 AM:
--------------------------------------------------------------------
JVM memory is not limitted in debian by default I think. Nodetool will not run by defualt with 4GB memory free.
So in debian packages it should be limitted in nodetool script.
was (Author: zenek_kraweznik0):
JVM memory is not limitted in debian by default I think. So in debian packages it should be limitted in nodetool script.
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-3124) java heap limit for nodetool
Posted by "Zenek Kraweznik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095940#comment-13095940 ]
Zenek Kraweznik commented on CASSANDRA-3124:
--------------------------------------------
# dpkg -l | grep java
ii java-common 0.40 Base of all Java packages
ii libcommons-daemon-java 1.0.2-2 library to launch Java applications as daemons
ii libjna-java 3.2.7-4 Dynamic access of native libraries from Java without JNI
ii sun-java6-bin 6.26-0squeeze1 Sun Java(TM) Runtime Environment (JRE) 6 (architecture dependent files)
ii sun-java6-jre 6.26-0squeeze1 Sun Java(TM) Runtime Environment (JRE) 6 (architecture independent files)
#
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-3124) java heap limit for nodetool
Posted by "Zenek Kraweznik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13102466#comment-13102466 ]
Zenek Kraweznik commented on CASSANDRA-3124:
--------------------------------------------
It seems that OpenVZ UBC is generating this error. If I use native kernel and run cassandra on host machine, not in virtual everything is fine.
But I still think that limitting heap size in nodetool script is good idea :)
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CASSANDRA-3124) java heap limit for nodetool
Posted by "Jonathan Ellis (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-3124.
---------------------------------------
Resolution: Fixed
Reviewer: jbellis
committed
> java heap limit for nodetool
> ----------------------------
>
> Key: CASSANDRA-3124
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3124
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Environment: not important
> Reporter: Zenek Kraweznik
> Assignee: Zenek Kraweznik
> Priority: Minor
> Fix For: 1.0.1
>
>
> 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
[jira] [Commented] (CASSANDRA-3124) java heap limit for nodetool
Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13101222#comment-13101222 ]
Eric Evans commented on CASSANDRA-3124:
---------------------------------------
{quote}
I have over 4GB memory free. Nodetool requires max 32MB memory to run and it shoud be limited to that value, no matter of default limits.
{quote}
Something sounds very strange here, because I read this to mean that the JVM is allocating about 3.9GB more memory than I'm seeing here.
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-3124) java heap limit for nodetool
Posted by "Zenek Kraweznik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13101055#comment-13101055 ]
Zenek Kraweznik commented on CASSANDRA-3124:
--------------------------------------------
JVM memory is not limitted in debian by default I think. So in debian packages it should be limitted in nodetool script.
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-3124) java heap limit for nodetool
Posted by "Jonathan Ellis (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-3124:
--------------------------------------
Component/s: (was: Core)
Affects Version/s: (was: 0.8.4)
(was: 0.8.3)
(was: 0.8.2)
(was: 0.8.1)
Fix Version/s: 1.0.1
Assignee: Zenek Kraweznik
> java heap limit for nodetool
> ----------------------------
>
> Key: CASSANDRA-3124
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3124
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Environment: not important
> Reporter: Zenek Kraweznik
> Assignee: Zenek Kraweznik
> Priority: Minor
> Fix For: 1.0.1
>
>
> 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
[jira] [Issue Comment Edited] (CASSANDRA-3124) java heap limit for
nodetool
Posted by "Zenek Kraweznik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095940#comment-13095940 ]
Zenek Kraweznik edited comment on CASSANDRA-3124 at 9/2/11 12:28 PM:
---------------------------------------------------------------------
I'm using packages from debian repository, if it's possible I'm using stable version
# dpkg -l | grep java
ii java-common 0.40 Base of all Java packages
ii libcommons-daemon-java 1.0.2-2 library to launch Java applications as daemons
ii libjna-java 3.2.7-4 Dynamic access of native libraries from Java without JNI
ii sun-java6-bin 6.26-0squeeze1 Sun Java(TM) Runtime Environment (JRE) 6 (architecture dependent files)
ii sun-java6-jre 6.26-0squeeze1 Sun Java(TM) Runtime Environment (JRE) 6 (architecture independent files)
#
was (Author: zenek_kraweznik0):
# dpkg -l | grep java
ii java-common 0.40 Base of all Java packages
ii libcommons-daemon-java 1.0.2-2 library to launch Java applications as daemons
ii libjna-java 3.2.7-4 Dynamic access of native libraries from Java without JNI
ii sun-java6-bin 6.26-0squeeze1 Sun Java(TM) Runtime Environment (JRE) 6 (architecture dependent files)
ii sun-java6-jre 6.26-0squeeze1 Sun Java(TM) Runtime Environment (JRE) 6 (architecture independent files)
#
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-3124) java heap limit for nodetool
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095998#comment-13095998 ]
Jonathan Ellis commented on CASSANDRA-3124:
-------------------------------------------
Oracle documentation says "The default heap size for all 32-bit J2SE implementations is 64MB. We have adjusted the defaults for 64-bit implementations to be 30% larger in order to make up for the increased size of Java objects due to larger native pointers."
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-3124) java heap limit for nodetool
Posted by "Jonathan Ellis (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (CASSANDRA-3124) java heap limit for nodetool
Posted by "Zenek Kraweznik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13097034#comment-13097034 ]
Zenek Kraweznik commented on CASSANDRA-3124:
--------------------------------------------
Oh, and 1 important thing: I haven't change any default java limit in java config, I've modyfied only cassandra-env.sh
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-3124) java heap limit for nodetool
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13097266#comment-13097266 ]
Jonathan Ellis commented on CASSANDRA-3124:
-------------------------------------------
So you're saying that 64 / 96 MB is _too large_ and you have to reduce it for nodetool to run?
I'd say there's something wrong with your environment.
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-3124) java heap limit for nodetool
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095939#comment-13095939 ]
Jonathan Ellis commented on CASSANDRA-3124:
-------------------------------------------
What JVM/platform are you running on that this is a problem?
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-3124) java heap limit for nodetool
Posted by "Zenek Kraweznik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13096636#comment-13096636 ]
Zenek Kraweznik commented on CASSANDRA-3124:
--------------------------------------------
I have over 4GB memory free. Nodetool requires max 32MB memory to run and it shoud be limited to that value, no matter of default limits.
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira