cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Boudreault (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8660) Cassandra makes Java 1.7+ SEGFAULT
Date Wed, 21 Jan 2015 02:33:34 GMT

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

Alan Boudreault commented on CASSANDRA-8660:
--------------------------------------------

[~belanger] How much data are on each node?

> Cassandra makes Java 1.7+ SEGFAULT
> ----------------------------------
>
>                 Key: CASSANDRA-8660
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8660
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: Linux Redhat 6.5
>            Reporter: Pierre Belanger
>            Priority: Critical
>         Attachments: hs_err_pid12004.log
>
>
> We upgraded a 3 nodes cluster from Cassandra 2.0.11-5f54285e9e to 2.1-7e6d9eb842.
> With Cassandra 2.1 , within ~10 min.  cassandra manages to makes Java 1.7.0_72-b14 segfault.
 This is also tested and same behavior w/ Java 1.7.0_60-b19 and 1.8.0_25-b17.
> We were able to use same data, downgrade back to 2.0 and things ran for ~3-4 days w/
no hick up.   Upgrading back to Cassandra-2.1, Java does a segfault again.
> See attached hs_err file.
> Pierre



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message