[
https://issues.apache.org/jira/browse/CASSANDRA-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13419564#comment-13419564
]
Trevor Robinson commented on CASSANDRA-4442:
--------------------------------------------
So apparently we don't want the minimum after all. :-
What type of system hit the failure? Java 6 on amd64, I'm guessing, since it
used to use 128k vs 104k.
Should the patch be changed to add a 25% margin? ((128 - 104) / 104 = ~0.23)
This would yield settings of 200k, 130k, and 80k for the systems mentioned in
my initial comment.
> 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.3
>
> Attachments:
> v1-0001-CASSANDRA-4275-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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
