[
https://issues.apache.org/jira/browse/CASSANDRA-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238556#comment-13238556
]
Wenjun commented on CASSANDRA-4078:
-----------------------------------
Paul
when I tried running code from [email protected]:thepaul/cassandra.git and I am
getting the following errors. The only changes I made in cassandra.yaml are
path to data files and local IP address.
java.lang.RuntimeException: org.apache.cassandra.config.ConfigurationException:
SimpleStrategy requires a replication_factor strategy option.
I don't really use git so I may have done something wrong to get your code.
The command I used is "git clone [email protected]:thepaul/cassandra.git". I
noticed your changes in IntervalNode.java were not included in the cloned code.
I copied the changes from 4078.add-aserts.txt. ant was able to build without
any issues. How do I make sure the new classe files are included in cassandra
runtime?
Attached is the complete log for startup.
Thanks
Wenjun
> StackOverflowError when upgrading to 1.0.8 from 0.8.10
> ------------------------------------------------------
>
> Key: CASSANDRA-4078
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4078
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.8.10
> Environment: OS: Linux xps.openfin 2.6.35.13-91.fc14.i686 #1 SMP Tue
> May 3 13:36:36 UTC 2011 i686 i686 i386 GNU/Linux
> Java: JVM vendor/version: Java HotSpot(TM) Server VM/1.6.0_31
> Reporter: Wenjun
> Assignee: paul cannon
> Priority: Critical
> Fix For: 0.8.10
>
> Attachments: 4078.add-asserts.txt, system.log, system.log.0326
>
>
> Hello
> I am trying to upgrade our 1-node setup from 0.8.10 to 1.0.8 and seeing the
> following exception when starting up 1.0.8. We have been running 0.8.10
> without any issues.
>
> Attached is the entire log file during startup of 1.0.8. There are 2
> exceptions:
> 1. StackOverflowError (line 2599)
> 2. InstanceAlreadyExistsException (line 3632)
> I tried "run scrub" under 0.8.10 first, it did not help. Also, I tried
> dropping the column family which caused the exception, it just got the same
> exceptions from another column family.
> Thanks
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
