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 6D69DFFBB for ; Tue, 2 Apr 2013 01:41:16 +0000 (UTC) Received: (qmail 57428 invoked by uid 500); 2 Apr 2013 01:41:16 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 57383 invoked by uid 500); 2 Apr 2013 01:41: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 57294 invoked by uid 99); 2 Apr 2013 01:41:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Apr 2013 01:41:16 +0000 Date: Tue, 2 Apr 2013 01:41:16 +0000 (UTC) From: "Arya Goudarzi (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CASSANDRA-5411) Unexpired hints can potentially create previously deleted rows 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-5411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arya Goudarzi updated CASSANDRA-5411: ------------------------------------- Description: Per discussion here: http://www.mail-archive.com/user@cassandra.apache.org/msg28905.html Hints are TTLed to lowest gc_grace_seconds. If we have hints that are not replayed, and the administrator updates schema to have lower gc_grace seconds on some CF, chances are compactions will delete tombstones and history of delete gets lost. If the deleted row is in some hints CF, since the TTL is not updated, chances are it gets replayed and the deleted row comes back to life. I think it would be nice as part of schema migration, to also update the TTLs on hints that already exists on any nodes hints column family. was: Per discussion here: http://www.mail-archive.com/user@cassandra.apache.org/msg28905.html Hits are TTLed to lowest gc_grace_seconds. If we have hints that are not replayed, and the administrator updates schema to have lower gc_grace seconds on some CF, chances are compactions will delete tombstones and history of delete gets lost. If the deleted row is in some hints CF, since the TTL is not updated, chances are it gets replayed and the deleted row comes back to life. I think it would be nice as part of schema migration, to also update the TTLs on hints that already exists on any nodes hints column family. > Unexpired hints can potentially create previously deleted rows > -------------------------------------------------------------- > > Key: CASSANDRA-5411 > URL: https://issues.apache.org/jira/browse/CASSANDRA-5411 > Project: Cassandra > Issue Type: Bug > Components: Core > Affects Versions: 1.1.10 > Environment: Ubuntu 10.04 > Reporter: Arya Goudarzi > > Per discussion here: http://www.mail-archive.com/user@cassandra.apache.org/msg28905.html > Hints are TTLed to lowest gc_grace_seconds. If we have hints that are not replayed, and the administrator updates schema to have lower gc_grace seconds on some CF, chances are compactions will delete tombstones and history of delete gets lost. If the deleted row is in some hints CF, since the TTL is not updated, chances are it gets replayed and the deleted row comes back to life. > I think it would be nice as part of schema migration, to also update the TTLs on hints that already exists on any nodes hints column family. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira