cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Trevor Robinson (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4442) Stack size settings in assume 64-bit x86
Date Sun, 11 Aug 2013 19:25:47 GMT


Trevor Robinson commented on CASSANDRA-4442:

Wasn't following up for lack of any way forward. :-) You didn't like my "a way" of starting
a JVM, and no one seemed in favor of a hard-coded version lookup table. I'm not sure what
package managers have to do with Apache Cassandra. Isn't it only distributed as a tarball
or an architecture-independent .deb?
> Stack size settings in assume 64-bit x86
> ---------------------------------------------------------
>                 Key: CASSANDRA-4442
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Trevor Robinson
>            Assignee: Trevor Robinson
>         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
For more information on JIRA, see:

View raw message