[
https://issues.apache.org/jira/browse/CASSANDRA-4275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283483#comment-13283483
]
Edward Capriolo commented on CASSANDRA-4275:
--------------------------------------------
I understand wanting to keep this setting low. But there must be some fairly
major underlying factor that made the JVM developers decided to raise the
minimum allowable from whatever it was to 160. While the increase is large
125K->250K the net effect on 1000 connections is not a big deal. 125MB vs 250MB
This is stack space not heap correct? Will using 100MB more stack be a problem
in the grand schema of Cassandra memory management? Also we do not want some
minimum setting that is likely to blow up on someone at the first sign of load.
I do not think it is a bad idea to dig in and determine if we can safely
code/tune cassandra to lower the setting. But I will un-assign myself if that
is the road we are going to take because that type of analysis is not my bread
and butter skill set.
> Oracle Java 1.7 u4 does not allow Xss128k
> -----------------------------------------
>
> Key: CASSANDRA-4275
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4275
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.9, 1.1.0
> Reporter: Edward Capriolo
> Assignee: Edward Capriolo
> Attachments: trunk-cassandra-4275.1.patch.txt
>
>
> Problem: This happens when you try to start it with default Xss setting of
> 128k
> =======
> The stack size specified is too small, Specify at least 160k
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> Solution
> =======
> Set -Xss to 256k
> Problem: This happens when you try to start it with Xss = 160k
> ========
> ERROR [Thrift:14] 2012-05-22 14:42:40,479 AbstractCassandraDaemon.java (line
> 139) Fatal exception in thread Thread[Thrift:14,5,main]
> java.lang.StackOverflowError
> Solution
> =======
> Set -Xss to 256k
--
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
