cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4843) When upgrading from 1.1.6 to 1.20 change in partitioner causes nodes not to start
Date Tue, 27 Nov 2012 15:33:58 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-4843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504677#comment-13504677
] 

Sylvain Lebresne commented on CASSANDRA-4843:
---------------------------------------------

+1
                
> 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
>            Assignee: Jonathan Ellis
>             Fix For: 1.2.0 rc1
>
>         Attachments: 4843.txt
>
>
> 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