Return-Path: Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: (qmail 62322 invoked from network); 20 Dec 2010 04:25:26 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 20 Dec 2010 04:25:26 -0000 Received: (qmail 49665 invoked by uid 500); 20 Dec 2010 04:25:25 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 49648 invoked by uid 500); 20 Dec 2010 04:25:25 -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 49623 invoked by uid 99); 20 Dec 2010 04:25:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Dec 2010 04:25:25 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Dec 2010 04:25:23 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oBK4P2ZG017866 for ; Mon, 20 Dec 2010 04:25:02 GMT Message-ID: <27981147.208611292819102214.JavaMail.jira@thor> Date: Sun, 19 Dec 2010 23:25:02 -0500 (EST) From: "Jonathan Ellis (JIRA)" To: commits@cassandra.apache.org Subject: [jira] Updated: (CASSANDRA-1884) sstable2json / sstablekeys should verify key order in -Data and -Index files In-Reply-To: <437871.196841292708401125.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/CASSANDRA-1884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-1884: -------------------------------------- Affects Version/s: (was: 0.7.0) Fix Version/s: 0.7.0 > sstable2json / sstablekeys should verify key order in -Data and -Index files > ---------------------------------------------------------------------------- > > Key: CASSANDRA-1884 > URL: https://issues.apache.org/jira/browse/CASSANDRA-1884 > Project: Cassandra > Issue Type: Improvement > Components: Tools > Reporter: Karl Mueller > Assignee: Karl Mueller > Priority: Minor > Fix For: 0.7.0 > > Attachments: c0.7-ordered-key-check.txt > > > Some cassandra users use sstable2json and sstablekeys to check -Data and -Index files for integrity. For example, if compaction fails, you can find out which files are causing the compaction to fail because they're corrupt. One type of corruption that can happen in both -Data and -Index files are keys getting out of order. (This shouldn't happen, but it can) Cassandra catches this error during compaction, but both tools didn't catch it. > This small patch simply causes an IO Exception during export if it finds out of order keys. > Some further work on it may make this optional with a command-line switch - it may be useful to export the data to json even though it's out of order to manually play it back, or have another script re-order it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.