[
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
