Andrey,
      Please see below for the answer to your questions.

On Friday, August 21, 2015 at 3:41:53 AM UTC-4, Andrey Lomakin wrote:
>
> Hi,
> 1. What version do you use ?
>
>>> Latest OrientDB 2.1 

> 2. Do you see data restore process after database startup ?
>
>>> No, I did not see nay data restore process. 

> 3. Do you use remote or embedded version ?
>
>>> I am using 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." ?
>
> >>> I killed JVM during the unit test of inserting new vertex and edges. 
Right after that, I started unit test again. Then OrientDB throw out an 
exception and indicates, that for the vertex I try to insert, there is a 
newer version (version 22) already in the OrientDB. The one I try to insert 
has the version 21.
 

> Did you load version from database, change vertex and store it and you get 
> this exception ?
>
>>> No, I called addVertex method to add new vertex.
 

> Did you run updates in parallel when you get this exception ?
>
>>> No, my unit test was single threaded. 

>  
>
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 ?
>
>>> This is the only exception I saw and it prevent me from going further.

Thanks,

Tai 

>
> On Thu, Aug 20, 2015 at 10:48 PM Tai Hu <[email protected] <javascript:>> 
> 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] <javascript:>.
>> 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.

Reply via email to