[ 
https://issues.apache.org/jira/browse/CASSANDRA-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

paul cannon updated CASSANDRA-4078:
-----------------------------------

    Attachment: 4078.add-asserts.txt

Wenjun, would it be possible to run your 1.0.8 version again (with DEBUG 
logging, as before) with this patch applied?

I haven't been able to figure out yet how this could get into an infinite 
recursion, but if we can identify an invalid assumption somewhere, that ought 
to help a lot.

If it's easier to get at, this change is also available in my github fork at 
g...@github.com:thepaul/cassandra.git (branch named 4078).
                
> 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
>
>
> 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

        

Reply via email to