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 479C6C647 for ; Wed, 17 Dec 2014 16:12:14 +0000 (UTC) Received: (qmail 7171 invoked by uid 500); 17 Dec 2014 16:12:13 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 7134 invoked by uid 500); 17 Dec 2014 16:12: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 7122 invoked by uid 99); 17 Dec 2014 16:12:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Dec 2014 16:12:13 +0000 Date: Wed, 17 Dec 2014 16:12:13 +0000 (UTC) From: "Sylvain Lebresne (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CASSANDRA-8462) Upgrading a 2.0 to 2.1 breaks CFMetaData on 2.0 nodes 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-8462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne updated CASSANDRA-8462: ---------------------------------------- Fix Version/s: 2.1.3 > Upgrading a 2.0 to 2.1 breaks CFMetaData on 2.0 nodes > ----------------------------------------------------- > > Key: CASSANDRA-8462 > URL: https://issues.apache.org/jira/browse/CASSANDRA-8462 > Project: Cassandra > Issue Type: Bug > Components: Core > Reporter: Rick Branson > Assignee: Aleksey Yeschenko > Fix For: 2.1.3 > > > Added a 2.1.2 node to a cluster running 2.0.11. Didn't make any schema changes. When I tried to reboot one of the 2.0 nodes, it failed to boot with this exception. Besides an obvious fix, any workarounds for this? > {noformat} > java.lang.IllegalArgumentException: No enum constant org.apache.cassandra.config.CFMetaData.Caching.{"keys":"ALL", "rows_per_partition":"NONE"} > at java.lang.Enum.valueOf(Enum.java:236) > at org.apache.cassandra.config.CFMetaData$Caching.valueOf(CFMetaData.java:286) > at org.apache.cassandra.config.CFMetaData.fromSchemaNoColumnsNoTriggers(CFMetaData.java:1713) > at org.apache.cassandra.config.CFMetaData.fromSchema(CFMetaData.java:1793) > at org.apache.cassandra.config.KSMetaData.deserializeColumnFamilies(KSMetaData.java:307) > at org.apache.cassandra.config.KSMetaData.fromSchema(KSMetaData.java:288) > at org.apache.cassandra.db.DefsTables.loadFromKeyspace(DefsTables.java:131) > at org.apache.cassandra.config.DatabaseDescriptor.loadSchemas(DatabaseDescriptor.java:529) > at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:270) > at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:496) > at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:585) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)