cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward Capriolo (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-4843) When upgrading from 1.1.6 to 1.20 change in partitioner causes nodes not to start
Date Sun, 21 Oct 2012 14:16:12 GMT
Edward Capriolo created CASSANDRA-4843:
------------------------------------------

             Summary: 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

Mime
View raw message