cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5517) Cassandra crashes at start with segmentation fault
Date Thu, 15 Aug 2013 13:39:48 GMT


Eric Evans commented on CASSANDRA-5517:

According to, recent Oracle JDK7 also needs a
larger stack. Maybe we should just increase it to 256 across the board; with a fairly solid
native protocol + HSHA story, keeping per-thread memory down isn't quite as important as it
was when we started.

That sounds reasonable to me, are we confident enough in this change to land it in cassandra-2.0.0?
Or cassandra-2.0 (my comfort sweet-spot, I think)?
> Cassandra crashes at start with segmentation fault
> --------------------------------------------------
>                 Key: CASSANDRA-5517
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: VirtualBox 4.2.6 VM with 4GB RAM, Xubuntu 12.10 as host and guest
> Cassandra 1.2.4 installed on guest as Debian package.
>            Reporter: Sergey Naumov
>            Assignee: Eric Evans
>            Priority: Minor
>         Attachments: 0001-CASSANDRA-5517-up-xss-to-256k-for-openjdk-1.6.patch, 0002-optional-upgrade-dependency-to-OpenJDK-7.patch
> Sometimes Cassandra fails at start with segmentation fault:
> # /usr/sbin/cassandra -f
> xss =   -ea -javaajent:/usr/share/cassandra/lib/jamm-0.2.5.jar -XX:+UseThreadPriorities
-XX:ThreadPriorityPolicy=42 -Xms1024M -Xmx1024M -Xmn100M -XX:+HeapDumpOnOutOfMemoryError -Xss180k
> Segmentation fault
> It seems that not only me encountered this bug:
> Solution proposed on this link works.

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