cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3179) JVM segfaults
Date Tue, 13 Sep 2011 21:07:09 GMT

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

Jonathan Ellis commented on CASSANDRA-3179:
-------------------------------------------

bq. SSTableReader.releaseReference() could see a refcount of 2, and not call the dfile.cleanup()

That means a read thread has a reference still, so cleanup will run when THAT thread releases
it.

> JVM segfaults
> -------------
>
>                 Key: CASSANDRA-3179
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3179
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0.0
>         Environment: java version "1.6.0_26"
> Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
> Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode)
>            Reporter: Brandon Williams
>            Assignee: Jonathan Ellis
>             Fix For: 1.0.0
>
>         Attachments: 3179-performance-test.txt, 3179-v2.txt, 3179.txt, hs_err_pid12074.log,
hs_err_pid28971.log, hs_err_pid7031.log
>
>
> Both with and without compressed OOPs enabled.  Seems to mostly happen during compaction+reads.
 I'll attach some hs_err files shortly.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message