You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Chris Goffinet (JIRA)" <ji...@apache.org> on 2010/08/02 09:40:20 UTC
[jira] Commented: (CASSANDRA-1345) Cassandra 0.6.3 fails to restart
if Cassandra 0.7 trunk (rev 981071) is run on the same data system store
[ https://issues.apache.org/jira/browse/CASSANDRA-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12894480#action_12894480 ]
Chris Goffinet commented on CASSANDRA-1345:
-------------------------------------------
I am not aware of any commitment from the other commiters, mentioning of supporting 'downwards' compatibility. It's just too much work.
> Cassandra 0.6.3 fails to restart if Cassandra 0.7 trunk (rev 981071) is run on the same data system store
> ---------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-1345
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1345
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7 beta 1
> Environment: Cassandra 0.6.3 , Cassandra 0.7 trunk rev 981071 , jdk1.6, Windows XP
> Reporter: Sanjay Sharma
> Priority: Minor
>
> The bigger question is whether downward compatibility is going to be supported on not!
> The steps were-
> a. Was running an application successfully on Cassandra 0.6.3 built from src on Win XP
> b. Ran Cassandra 0.7 trunk rev 981071 without changing any conf parameters. The server ran successfully.
> c. Stopped 0.7 server
> d. Started 0.6.3 version- exception was reported.
> The trace is-
> D:\data\dev\trials\nosql\apache-cassandra-0.6.3-src\bin>set CASSANDRA_HOME=D:\data\dev\trials\nosql\apache-cassandra-0.6.3-src
> Starting Cassandra Server
> Listening for transport dt_socket at address: 8888
> INFO 12:40:33,921 Auto DiskAccessMode determined to be standard
> INFO 12:40:34,296 Sampling index for D:\var\lib\cassandra\data\system\LocationInfo-e-47-Data.db
> ERROR 12:40:34,296 Exception encountered during startup.
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(String.java:1938)
> at org.apache.cassandra.dht.RandomPartitioner.convertFromDiskFormat(RandomPartitioner.java:50)
> at org.apache.cassandra.io.SSTableReader.loadIndexFile(SSTableReader.java:259)
> at org.apache.cassandra.io.SSTableReader.open(SSTableReader.java:121)
> at org.apache.cassandra.io.SSTableReader.open(SSTableReader.java:110)
> at org.apache.cassandra.db.ColumnFamilyStore.<init>(ColumnFamilyStore.java:178)
> at org.apache.cassandra.db.ColumnFamilyStore.createColumnFamilyStore(ColumnFamilyStore.java:248)
> at org.apache.cassandra.db.Table.<init>(Table.java:338)
> at org.apache.cassandra.db.Table.open(Table.java:199)
> at org.apache.cassandra.db.SystemTable.checkHealth(SystemTable.java:124)
> at org.apache.cassandra.thrift.CassandraDaemon.setup(CassandraDaemon.java:94)
> at org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java:211)
> Exception encountered during startup.
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(String.java:1938)
> at org.apache.cassandra.dht.RandomPartitioner.convertFromDiskFormat(RandomPartitioner.java:50)
> at org.apache.cassandra.io.SSTableReader.loadIndexFile(SSTableReader.java:259)
> at org.apache.cassandra.io.SSTableReader.open(SSTableReader.java:121)
> at org.apache.cassandra.io.SSTableReader.open(SSTableReader.java:110)
> at org.apache.cassandra.db.ColumnFamilyStore.<init>(ColumnFamilyStore.java:178)
> at org.apache.cassandra.db.ColumnFamilyStore.createColumnFamilyStore(ColumnFamilyStore.java:248)
> at org.apache.cassandra.db.Table.<init>(Table.java:338)
> at org.apache.cassandra.db.Table.open(Table.java:199)
> at org.apache.cassandra.db.SystemTable.checkHealth(SystemTable.java:124)
> at org.apache.cassandra.thrift.CassandraDaemon.setup(CassandraDaemon.java:94)
> at org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java:211)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.