Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-7353

Java heap being set too large on Windows with 32-bit JVM

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Low
    • Resolution: Fixed
    • 2.1 rc2
    • Packaging
    • Windows Server 2008, 8G RAM, 32-bit JVM

    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.

      Attachments

        1. 7353_v1.txt
          2 kB
          Joshua McKenzie
        2. 7353_v2.txt
          2 kB
          Joshua McKenzie
        3. 7353_v3.txt
          2 kB
          Joshua McKenzie

        Activity

          People

            JoshuaMcKenzie Joshua McKenzie
            philipthompson Philip Thompson
            Joshua McKenzie
            Philip Thompson
            Philip Thompson Philip Thompson
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: