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 28B77EB96 for ; Thu, 13 Dec 2012 14:04:20 +0000 (UTC) Received: (qmail 74086 invoked by uid 500); 13 Dec 2012 14:04:19 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 73669 invoked by uid 500); 13 Dec 2012 14:04:18 -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 73487 invoked by uid 99); 13 Dec 2012 14:04:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Dec 2012 14:04:12 +0000 Date: Thu, 13 Dec 2012 14:04:12 +0000 (UTC) From: "Marcus Eriksson (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (CASSANDRA-5061) Upgraded cassandra loses all cfs on restart 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-5061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson reassigned CASSANDRA-5061: ------------------------------------------ Assignee: Marcus Eriksson > Upgraded cassandra loses all cfs on restart > ------------------------------------------- > > Key: CASSANDRA-5061 > URL: https://issues.apache.org/jira/browse/CASSANDRA-5061 > Project: Cassandra > Issue Type: Bug > Affects Versions: 1.1.7 > Reporter: Marcus Eriksson > Assignee: Marcus Eriksson > Attachments: 0001-flush-data-after-fixing-nano-timestamps.patch > > > A bit dramatic summary, but hey; > If you upgrade cassandra and then restart it, you lose all your CFs, but they come back if you restart again. > This is due to fixSchemaNanoTimestamp not flushing the new data after truncating the CF and re-doing the mutations. -- 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