Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 35B5F10209 for ; Thu, 30 Jan 2014 18:02:20 +0000 (UTC) Received: (qmail 69160 invoked by uid 500); 30 Jan 2014 18:02:17 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 69124 invoked by uid 500); 30 Jan 2014 18:02:16 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 69101 invoked by uid 99); 30 Jan 2014 18:02:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Jan 2014 18:02:15 +0000 Date: Thu, 30 Jan 2014 18:02:15 +0000 (UTC) From: "Jason Brown (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-6503) sstables from stalled repair sessions become live after a reboot and can resurrect deleted data MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-6503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886836#comment-13886836 ] Jason Brown commented on CASSANDRA-6503: ---------------------------------------- Committed the 1.2 patch to 1.2, have a few questions for [~yukim] that I'll here in a minute (after coffee) > 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: Jason Brown > Priority: Minor > Fix For: 1.2.14, 2.0.5 > > Attachments: 6503_2.0-v2.diff, 6503_2.0-v3.diff, 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)