[
https://issues.apache.org/jira/browse/CASSANDRA-3179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13103419#comment-13103419
]
Yang Yang commented on CASSANDRA-3179:
--------------------------------------
btw, as I was trying to going through the code to understand the problem, I
found it seems that the MMapedSegmentedFile.cleanup() code could be skipped in
some sequences of mixed read and compact:
read increases the refcount, then
DataTracker.replaceCompactedSSTables()---->....--->
SSTableReader.releaseReference() could see a refcount of 2, and not call the
dfile.cleanup()
it's not a big problem ( code seems to run fine with the cleanup() lines
commented out), but that kind of thwarts the purpose of adding them in
> 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: Sylvain Lebresne
> 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
