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 40E66D3DC for ; Sun, 21 Oct 2012 14:18:12 +0000 (UTC) Received: (qmail 85332 invoked by uid 500); 21 Oct 2012 14:18:12 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 85312 invoked by uid 500); 21 Oct 2012 14:18:11 -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 85301 invoked by uid 99); 21 Oct 2012 14:18:11 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 21 Oct 2012 14:18:11 +0000 Date: Sun, 21 Oct 2012 14:18:11 +0000 (UTC) From: "Edward Capriolo (JIRA)" To: commits@cassandra.apache.org Message-ID: <1223519414.7299.1350829091877.JavaMail.jiratomcat@arcas> In-Reply-To: <651373149.7298.1350828972121.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (CASSANDRA-4843) When upgrading from 1.1.6 to 1.20 change in partitioner causes nodes not to start 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-4843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13480973#comment-13480973 ] Edward Capriolo commented on CASSANDRA-4843: -------------------------------------------- The error message is strange as well. Changing paritioner on a existing cluster can cause data loose, Please verify your partitioner in cassandra.yaml "Can cause data *loss" is impossible because Cassandra will not even start. If it did start it would definitely cause data loss. > When upgrading from 1.1.6 to 1.20 change in partitioner causes nodes not to start > --------------------------------------------------------------------------------- > > Key: CASSANDRA-4843 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4843 > Project: Cassandra > Issue Type: Bug > Reporter: Edward Capriolo > > ERROR 10:17:20,341 Cannot open /home/edward/cassandra/data/system/schema_keyspaces/system-schema_keyspaces-hf-1 because partitioner does not match org.apache.cassandra.dht.RandomPartitioner != org.apache.cassandra.dht.Murmur3Partitioner > This is because 1.2 has a new default partitioner, why are we changing the default? Is this wise? The current partitioner has been rock solid for years. > Should the previously known partition be stored in the schema like the previously know seed nodes, and schema? -- 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