cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4442) Stack size settings in assume 64-bit x86
Date Sat, 21 Jul 2012 14:07:34 GMT


Brandon Williams commented on CASSANDRA-4442:

bq. Should the patch be changed to add a 25% margin? 

I don't think a fudge factor is something I want in the stack size.  If we have to, I'd prefer
explicit arch detection along with the version and have the decision based on those.
> Stack size settings in assume 64-bit x86
> ---------------------------------------------------------
>                 Key: CASSANDRA-4442
>                 URL:
>             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:!default.jspa
For more information on JIRA, see:


View raw message