freeze lock for update

[martingg88]

@Laa seem like it still lock when doing update/insert. here the thread dump for your debugging. In between we have some discussion at #4090

you can get the thread dump for your debugging.

https://drive.google.com/file/d/0B4HzIyaEAQ5WUDhoM2h4Sm56SDQ/view?usp=sharing

[andrii0lomakin]

Do you have Skype so we may chat and debug or merey code to reproduce this issue ?

[martingg88]

here is my skype ckgan2004@hotmail.com. what time you about want to do dis discussion?

[andrii0lomakin]

what about now ))

[martingg88]

sorry.. i can't make it now...how about 2 hour later at 21:00+0800 malaysia time?

[andrii0lomakin]

2 hours later is ok for me

[martingg88]

ok...see u later..

[andrii0lomakin]

I can not find your contact in Skype, could you connect to me lomakin_andrey .

[martingg88]

sure..i will do it later...

[martingg88]

@Laa... as for last conversation over skype. are you able to reproduce this issue?

[andrii0lomakin]

Hi, Sorry I am super busy by issue #4144 . Once I finish it I will be back
to this one .
On May 28, 2015 6:32 PM, "martingg88" notifications@github.com wrote:

@Laa https://github.com/laa... as for last conversation over skype. are
you able to reproduce this issue?

—
Reply to this email directly or view it on GitHub
#4206 (comment)
.

[martingg88]

sure. thanks

[andrii0lomakin]

Hi, coudl you try this distribution https://www.dropbox.com/s/xs2w59sncv9ln4m/orientdb-community-2.1-SNAPSHOT-distribution.zip?dl=0 . Does deadlock still persist ?

[martingg88]

i will try it today or tomorrow and let you know the result. thanks.

[andrii0lomakin]

Thank you for your help !

[martingg88]

I still facing the issue as follows after tested.
this should be the concurrent issue for update.
OrientDB.RequestError: Error on saving record #59:11062

On Fri, Jun 5, 2015 at 9:55 PM, Andrey Lomakin notifications@github.com
wrote:

Thank you for your help !

—
Reply to this email directly or view it on GitHub
#4206 (comment)
.

[martingg88]

I have the issue as follows after tested.
this happen for both execute update one after another and in parallel/concurrent.
OrientDB.RequestError: Error on saving record #59:11062

[andrii0lomakin]

Could you send me stack trace from server log for this error ?

[andrii0lomakin]

Is it correct that there is no freeze now, but there is issue which you reported ?

[martingg88]

1. this seems like another issue which relate to the following exception.
   com.orientechnologies.orient.core.exception.ODatabaseException: Error on
   saving record in cluster Define a method to call against the POJO after unmarshalling [moved] #56 [ONetworkProtocolBinary]
2. I can't see any freeze there since i had have this issue ever.

On Mon, Jun 8, 2015 at 6:13 PM, Andrey Lomakin notifications@github.com
wrote:

Is it correct that there is no freeze now, but there is issue which you
reported ?

—
Reply to this email directly or view it on GitHub
#4206 (comment)
.

[lvca]

It's already released in 2.0.12 and 2.1-rc5

[martingg88]

ok..will try it as soon as possible

[martingg88]

In between, if i can't reply you in timely manner. You can ask @Laa to test it as he have my test script for two cases (etc: concurrent update and transaction roll back issue). Thanks.

[martingg88]

test script working fine for orientjs- 2.0.0 and orientdb-2.1-rc5 enterprise version.

1. test run update 1000 records with lock mechanism in concurrent/parallel.
   • passed without error.
   • it takes 2919ms to complete. 2919ms is acceptable performance to handle 1000 records?

[lvca]

How you did insert those records?

[martingg88]

can you get the test script from @Laa. he have the test script for both update and commit in concurrent.
from the test scripts, you should be able to see how i update the records. thanks.

[martingg88]

any update?

[wolf4ood]

@martingg88

have you solved this?

[martingg88]

You should check with your team members please.

[wolf4ood]

@martingg88

this should been fixed
can you confirm that?

[wolf4ood]

@martingg88

i'm closing this. If you still have problem with this issue, you can reopen it