Hi, 1. What version do you use ? 2. Do you see data restore process after database startup ? 3. Do you use remote or embedded version ?
What do you mean by "I got some error message about some of vertex has a different version from my current vertex version." ? Did you load version from database, change vertex and store it and you get this exception ? Did you run updates in parallel when you get this exception ? If you do hard kill of jvm in the middle of transaction you will any way have database in inconsistent state and during restart transaction will be rolled back. What additional signs of DB corruption have you send aside of concurrent version modification exception ? On Thu, Aug 20, 2015 at 10:48 PM Tai Hu <[email protected]> wrote: > Hi all, > I am working on a project to port from neo4j to OrientDB. Today > during my debug process, I kill the JVM before a transaction finished. Then > my OrientDB is corrupted. When I try to start it again, I got some error > message about some of vertex has a different version from my current vertex > version. I found this issue is very easy to reproduce, just need to kill > JVM during a long delete or update transaction and OrientDB will be > corrupted. Since we are developing a desktop solution, so it will be very > common that user kill the app at any moment, my question is "Is there a way > to recover from those of corruption?" > > Thanks, > > Tai > > -- > > --- > You received this message because you are subscribed to the Google Groups > "OrientDB" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
