[
https://issues.apache.org/jira/browse/CASSANDRA-2381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012201#comment-13012201
]
Hudson commented on CASSANDRA-2381:
-----------------------------------
Integrated in Cassandra-0.7 #411 (See
[https://hudson.apache.org/hudson/job/Cassandra-0.7/411/])
r/m unnecessary isDropped check from maybeSwitchMemtable (the one in
Memtable.writeSortedContents it the important one)
patch by jbellis for CASSANDRA-2381
add actual dropped check to Memtable.flush for CASSANDRA-2381
patch by jbellis
fix migration race vs flush
patch by jbellis; reviewed by gdusbabek for CASSANDRA-2381
> orphaned data files may be created during migration race
> --------------------------------------------------------
>
> Key: CASSANDRA-2381
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2381
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7.0
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Priority: Minor
> Fix For: 0.7.5
>
> Attachments: 2381-0.8.txt, 2381-v3.txt, 2831-v2.txt
>
>
> We try to prevent creating orphans by locking Table.flusherLock in
> maybeSwitchMemtable and the Migration process, but since the actual writing
> is done asynchronously in Memtable.writeSortedContents there is a race
> window, where we acquire lock in maybeSwitch, we're not dropped so we queue
> the flush and release the lock, Migration does the drop, then Memtable writes
> itself out.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
