You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Philip Thompson (JIRA)" <ji...@apache.org> on 2014/06/05 01:03:02 UTC
[jira] [Updated] (CASSANDRA-7353) Java heap being set too large on
Windows with 32-bit JVM
[ https://issues.apache.org/jira/browse/CASSANDRA-7353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Philip Thompson updated CASSANDRA-7353:
---------------------------------------
Description:
On windows, the JVM settings for max heap size and new gen heap size are set based on the total system memory. When the system has 8G of RAM, the max heap size is set to 2048M. However, according to http://goo.gl/1ElbLm, the recommended max heap for a 32 bit JVM on Windows is 1.8G.
When cassandra is started on Windows under these conditions, the following error is seen:
Error occurred during initialization of VM
Could not reserve enough space for object heap
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
Switching to a 64-bit JVM on the same machine solves the issue. If a 32-bit JVM is being used, cassandra should be started up with a smaller heap than would be normally used to prevent the error.
was:
On windows, the JVM settings for max heap size and new gen heap size are set based on the total system memory. When the system has 8G of RAM, the max heap size is set to 2048M. However, according to http://goo.gl/1ElbLm, the recommended max heap for a 32 bit JVM on Windows is 1.8G.
When cassandra is started on Windows under these conditions, the following error is seen:
Error occurred during initialization of VM
Could not reserve enough space for object heap
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
> Java heap being set too large on Windows with 32-bit JVM
> --------------------------------------------------------
>
> Key: CASSANDRA-7353
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7353
> Project: Cassandra
> Issue Type: Bug
> Environment: Windows Server 2008, 8G RAM, 32-bit JVM
> Reporter: Philip Thompson
> Assignee: Joshua McKenzie
> Priority: Minor
> Labels: Windows
>
> On windows, the JVM settings for max heap size and new gen heap size are set based on the total system memory. When the system has 8G of RAM, the max heap size is set to 2048M. However, according to http://goo.gl/1ElbLm, the recommended max heap for a 32 bit JVM on Windows is 1.8G.
> When cassandra is started on Windows under these conditions, the following error is seen:
> Error occurred during initialization of VM
> Could not reserve enough space for object heap
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> Switching to a 64-bit JVM on the same machine solves the issue. If a 32-bit JVM is being used, cassandra should be started up with a smaller heap than would be normally used to prevent the error.
--
This message was sent by Atlassian JIRA
(v6.2#6252)