cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Brown (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6503) sstables from stalled repair sessions become live after a reboot and can resurrect deleted data
Date Tue, 07 Jan 2014 01:29:50 GMT

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

Jason Brown commented on CASSANDRA-6503:
----------------------------------------

bq. we probably want some kind of lockfile

Interesting. What problems do you see this solving (I'm probably missing something in my understanding)?

bq. splitting FileMessage is better than casting

Yeah, I knew you were gonna say that :)

> sstables from stalled repair sessions become live after a reboot and can resurrect deleted
data
> -----------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-6503
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6503
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jeremiah Jordan
>            Assignee: Yuki Morishita
>            Priority: Minor
>             Fix For: 1.2.14, 2.0.5
>
>         Attachments: 6503_c1.2-v1.patch
>
>
> The sstables streamed in during a repair session don't become active until the session
finishes.  If something causes the repair session to hang for some reason, those sstables
will hang around until the next reboot, and become active then.  If you don't reboot for 3
months, this can cause data to resurrect, as GC grace has expired, so tombstones for the data
in those sstables may have already been collected.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message