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 6C4DC18372 for ; Thu, 25 Jun 2015 18:57:05 +0000 (UTC) Received: (qmail 50844 invoked by uid 500); 25 Jun 2015 18:57:05 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 50794 invoked by uid 500); 25 Jun 2015 18:57:05 -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 50530 invoked by uid 99); 25 Jun 2015 18:57:05 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Jun 2015 18:57:05 +0000 Date: Thu, 25 Jun 2015 18:57:05 +0000 (UTC) From: "Philip Thompson (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CASSANDRA-9654) Failure to open sstable after upgrade to 2.1 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-9654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philip Thompson updated CASSANDRA-9654: --------------------------------------- Attachment: sstables.tar.gz I've tarred up a few sstables on a new cluster. Here is the log error there: {code} ERROR [SSTableBatchOpen:1] 2015-06-25 18:07:57,115 SSTableReader.java:435 - Cannot open /tmp/dtest-Cwg0RO/test/node1/data/upgrade/cf/la-7-big; partitioner org.apache.cassandra.dht.LocalPartitioner does not match system partitioner org.apache.cassandra.dht.RandomPartitioner. Note that the default partitioner starting with Cassandra 1.2 is Murmur3Partitioner, so you will need to edit that to match your old partitioner if upgrading. ERROR [SSTableBatchOpen:2] 2015-06-25 18:07:57,123 SSTableReader.java:435 - Cannot open /tmp/dtest-Cwg0RO/test/node1/data/upgrade/cf/la-10-big; partitioner org.apache.cassandra.dht.LocalPartitioner does not match system partitioner org.apache.cassandra.dht.RandomPartitioner. Note that the default partitioner starting with Cassandra 1.2 is Murmur3Partitioner, so you will need to edit that to match your old partitioner if upgrading. {code} > Failure to open sstable after upgrade to 2.1 > -------------------------------------------- > > Key: CASSANDRA-9654 > URL: https://issues.apache.org/jira/browse/CASSANDRA-9654 > Project: Cassandra > Issue Type: Bug > Components: Core > Reporter: Philip Thompson > Assignee: Branimir Lambov > Fix For: 2.1.x > > Attachments: node1.log, node2.log, node3.log, sstables.tar.gz > > > After upgrading a 3 node cluster on the path 1.2.19 -> 2.0.16 -> 2.1.7, I see this error in the logs on 2.1.7 > {code} > ERROR [SSTableBatchOpen:1] 2015-06-25 17:16:55,424 SSTableReader.java:435 - Cannot open /tmp/dtest-Ibi6zm/test/node1/data/upgrade/cf/la-7-big; partitioner org.apache.cassandra.dht.LocalPartitioner does not match system partitioner org.apache.cassandra.dht.Murmur3Partitioner. Note that the default partitioner starting with Cassandra 1.2 is Murmur3Partitioner, so you will need to edit that to match your old partitioner if upgrading. > ERROR [SSTableBatchOpen:2] 2015-06-25 17:16:55,425 SSTableReader.java:435 - Cannot open /tmp/dtest-Ibi6zm/test/node1/data/upgrade/cf/la-10-big; partitioner org.apache.cassandra.dht.LocalPartitioner does not match system partitioner org.apache.cassandra.dht.Murmur3Partitioner. Note that the default partitioner starting with Cassandra 1.2 is Murmur3Partitioner, so you will need to edit that to match your old partitioner if upgrading. > {code} > Node logs are attached. > To reproduce, you'll need to run the upgrade dtest as follows: > {{nosetests -sv upgrade_through_versions_test.py:TestUpgradeThroughVersions.upgrade_test}}. I don't have CI results for this yet, nor will I soon. To run this, you'll need both JDK7 and JDK8 installed, for compilation reasons. Set the env vars JAVA7_HOME and JAVA8_HOME, respectively. I'll work on finding an sstable that represent the issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)