[ https://issues.apache.org/jira/browse/CASSANDRA-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13461982#comment-13461982 ]
Jonathan Ellis commented on CASSANDRA-4442: ------------------------------------------- Note that recent 1.6 JVMs need more than the minimum stack size to actually do network operations; we're using Xss=180, where the minimum is 160. > Stack size settings in cassandra-env.sh assume 64-bit x86 > --------------------------------------------------------- > > Key: CASSANDRA-4442 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4442 > Project: Cassandra > Issue Type: Bug > Components: Core > Affects Versions: 1.1.2 > Reporter: Trevor Robinson > Assignee: Trevor Robinson > Fix For: 1.1.6 > > Attachments: > v1-0001-CASSANDRA-4275-Use-JVM-s-reported-minimum-stack-size-o.txt, > v1-0001-CASSANDRA-4442-Use-JVM-s-reported-minimum-stack-size-o.txt > > > The fix for CASSANDRA-4275 hard-codes a 160 KB stack size when using Java 7 > on Linux. This assumes the Oracle 7u4 JVM on 64-bit x86. For systems like > 32-bit ARM, this size is excessive (the minimum for 7u4 on ARM is 60-64 KB). > Also, the minimum allowed value is version-dependent and is calculated > dynamically by the JVM on startup based on Linux parameters that can also > change. A better approach would be to query the JVM for the minimum stack > size. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira