[
https://issues.apache.org/jira/browse/CASSANDRA-7352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14018090#comment-14018090
]
Joshua McKenzie edited comment on CASSANDRA-7352 at 6/4/14 8:04 PM:
--------------------------------------------------------------------
Attaching a v1 to truncate - give it a whirl and let me know if that cleans it
up. (note: I'd test it myself but all my machines are multiples that are
behaving atm)
was (Author: joshuamckenzie):
Attaching a v1 to truncate - give it a whirl and let me know if that cleans it
up.
> Java heap flags are being set to invalid values on Windows
> ----------------------------------------------------------
>
> Key: CASSANDRA-7352
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7352
> Project: Cassandra
> Issue Type: Bug
> Environment: Windows
> Reporter: Philip Thompson
> Assignee: Joshua McKenzie
> Labels: Windows
> Attachments: 7352_v1.txt
>
>
> In conf/cassandra-env.ps1 max heap size is set based on system memory. New
> generation heap size is then set based on max heap size. Integer division is
> not used, and thus floating point results are possible, which will prevent
> cassandra from being started up. The following error is seen:
> Invalid initial eden size: -Xmn511.75M
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
