Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id E8431200B13 for ; Tue, 10 May 2016 15:50:14 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id E7028160877; Tue, 10 May 2016 13:50:14 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 2CEB9160A12 for ; Tue, 10 May 2016 15:50:14 +0200 (CEST) Received: (qmail 48435 invoked by uid 500); 10 May 2016 13:50:13 -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 48334 invoked by uid 99); 10 May 2016 13:50:13 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 May 2016 13:50:13 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 0E1E62C14F8 for ; Tue, 10 May 2016 13:50:13 +0000 (UTC) Date: Tue, 10 May 2016 13:50:13 +0000 (UTC) From: "Tommy Stendahl (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CASSANDRA-11742) Failed bootstrap results in exception when node is restarted MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 10 May 2016 13:50:15 -0000 [ https://issues.apache.org/jira/browse/CASSANDRA-11742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommy Stendahl updated CASSANDRA-11742: --------------------------------------- Attachment: 11742.txt > Failed bootstrap results in exception when node is restarted > ------------------------------------------------------------ > > Key: CASSANDRA-11742 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11742 > Project: Cassandra > Issue Type: Bug > Reporter: Tommy Stendahl > Assignee: Tommy Stendahl > Priority: Minor > Attachments: 11742.txt > > > Since 2.2 a failed bootstrap results in a {{org.apache.cassandra.exceptions.ConfigurationException: Found system keyspace files, but they couldn't be loaded!}} exception when the node is restarted. This did not happen in 2.1, it just tried to bootstrap again. I know that the workaround is relatively easy, just delete the system keyspace in the data folder on disk and try again, but its a bit annoying that you have to do that. > The problem seems to be that the creation of the {{system.local}} table has been moved to just before the bootstrap begins (in 2.1 it was done much earlier) and as a result its still in the memtable och commitlog if the bootstrap failes. Still a few values is inserted to the {{system.local}} table at an earlier point in the startup and they have been flushed from the memtable to an sstable. When the node is restarted the {{SystemKeyspace.checkHealth()}} is executed before the commitlog is replayed and therefore only see the sstable with an incomplete {{system.local}} table and throws an exception. > I think we could fix this very easily by forceFlush the system keyspace in the {{StorageServiceShutdownHook}}, I have included a patch that does this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)