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 E163D186B8 for ; Tue, 18 Aug 2015 00:50:46 +0000 (UTC) Received: (qmail 59627 invoked by uid 500); 18 Aug 2015 00:50:46 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 59594 invoked by uid 500); 18 Aug 2015 00:50:46 -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 59577 invoked by uid 99); 18 Aug 2015 00:50:46 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Aug 2015 00:50:46 +0000 Date: Tue, 18 Aug 2015 00:50:46 +0000 (UTC) From: "Stefania (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-10112) Apply disk_failure_policy to transaction logs 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-10112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14700537#comment-14700537 ] Stefania commented on CASSANDRA-10112: -------------------------------------- I think we should stash files when the {{disk_failure_policy}} is {{ignore}}, or we could add a new policy for this. I'm not sure for the case when we refuse to start though. Perhaps in this case we should add this functionality to the offline sstable utility tool and let the operator either clean-up or stash. > Apply disk_failure_policy to transaction logs > --------------------------------------------- > > Key: CASSANDRA-10112 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10112 > Project: Cassandra > Issue Type: Improvement > Reporter: Stefania > Assignee: Stefania > > Transaction logs were introduced by CASSANDRA-7066 and are read during start-up. In case of file system errors, such as disk corruption, we currently log a panic error and leave the sstable files and transaction logs as they are; this is to avoid rolling back a transaction (i.e. deleting files) by mistake. > We should instead look at the {{disk_failure_policy}} and refuse to start unless the failure policy is {{ignore}}. > We should also consider stashing files that cannot be read during startup, either transaction logs or sstables, by moving them to a dedicated sub-folder. -- This message was sent by Atlassian JIRA (v6.3.4#6332)