cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard Low (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-2441) Cassandra crashes with segmentation fault on Debian 5.0 and Ubuntu 10.10
Date Thu, 12 Apr 2012 09:43:26 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252306#comment-13252306
] 

Richard Low commented on CASSANDRA-2441:
----------------------------------------

Tracked this down to the stack size setting.  In cassandra-env.sh, the stack size is set to
128k.  From running gdb, the segfault is tracked down to a stack overflow in parse_manifest.c:234
within openjdk.  It's clear what's going on: there's a huge statically allocated variable.

Setting the stack size to 256k means Cassandra can start up with javaagent.  So we could reenable
this for openjdk if people are prepared to take the memory hit on stack size.
                
> Cassandra crashes with segmentation fault on Debian 5.0 and Ubuntu 10.10
> ------------------------------------------------------------------------
>
>                 Key: CASSANDRA-2441
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2441
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.8 beta 1
>         Environment: Both servers have identical hardware configuration: Quad-Core AMD
Opteron(tm) Processor 2374 HE, 4 GB RAM (rackspace servers)
> Java version "1.6.0_20"
> OpenJDK Runtime Environment (IcedTea6 1.9.7) (6b20-1.9.7-0ubuntu1)
> OpenJDK 64-Bit Server VM (build 19.0-b09, mixed mode)
>            Reporter: Pavel Yaskevich
>            Assignee: Jonathan Ellis
>            Priority: Critical
>             Fix For: 0.8 beta 1
>
>         Attachments: 2441.txt, 2441.txt, jamm-0.2.1.jar
>
>
> Last working commit is c8d1984bf17cab58f40069e522d074c7b0077bc1 (merge from 0.7), branch:
trunk.
> What I did is cloned git://git.apache.org/cassandra.git and did git reset each commit
with `ant clean && ant && ./bin/cassandra -f` until I got cassandra started

--
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

        

Mime
View raw message