-
Notifications
You must be signed in to change notification settings - Fork 871
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DB halt when read/write simultaneously same class through different connections #6507
Comments
Hi could you send us full thread dump when OreintDB halt ? |
Also seems like you switched off autostart of transactions. Did you commit transactions at the end ? Seem like TX so big that you started to have huge GC pauses. |
When system halt, there is no thread dump. How to turn it on? |
The hardware and software environment are:
Data volume is about 400M of .tar.gz file of the database folder. A single class may consists of 300,000 records. As the data vaolume is relatively small, the hardware usage is always very low, memory consumption is less than 15%, CPU consumption is less that 5 percent. When OrientDB halt happen, comment 'orientdb.sh stop' couldn't stop the java process, must use 'kill -9' to kill the process. |
Updated issue title as 'DB halt when read/write simultaneously same class through different connections'. Steps to reproduce:
|
Hi because that MT issue (actually we fixed similar two days ago) we need thread dump to fix the given problem. Could you send us thread dump when DB halts, to send thread dump you may use the following command: |
@zhengguozhu if you have any problems with getting of stack trace, could you notify me in issue and I will try to help you. |
Hi @zhengguozhu could you send us thread dump ? |
I adjusted the server settings to: JAVA_OPTS="-XX:+PerfDisableSharedMem" It is not easy to reproduce the issue now. |
@zhengguozhu thank you very much for your effort. We have fixed several deadlocks in 2.2.7 and 2.2.8 so I have hope that your issue is fixed too. But in case of any hint of deadlock (when database becomes frozen from your point of view) the thread dump is really helpful to identify and fix problem. |
JAVA_OPTS="-XX:+PerfDisableSharedMem" I removed above settings, and able to reproduce. |
Just tried to add back the settings, and it was able to reproduce the problem again. |
@zhengguozhu is your server still locked , if that is true could you create heap dump too ? if not could you reproduce deadlock again (sorry for that) and send me thread dump again and heap dump. To make heap dump please execute |
I am able to reproduce with 2.2.8. |
The heap dump file is too big, 181M, can't send. |
@zhengguozhu I may share my google drive with you . May I do it ? Very important though to have thread dump and heap dump are taken from the same time. |
Alright, I will create a user for you on my server, then you can scp to get the files. |
@iaa, have sent to your gmail. |
@zhengguozhu heap dump download in progress but speed is very slow meanwhile could you answer the question do you use standard distribution of server with default settings, do not you ? |
@zhengguozhu if you look at server log do you see any logged exceptions ? |
The server is standard distribution of server with below settings: No logged exceptions. Let me know once you downloaded the dump file. |
@zhengguozhu thank you very much for your help I found the reason of issue and will fix it in a couple of hours. Very appreciate that you spent your time and helped us to diagnose the issue. |
@zhengguozhu fixed , could you check it in latest 2.2.x branch. To build project simply run |
I can't build on my machine. Any clue with following error? constituent[36]: file:/usr/share/maven/lib/maven-wagon_http-shaded.jar constituent[37]: file:/usr/share/maven/lib/maven-wagon_provider-api.jarException in thread "main" java.lang.InternalError |
@zhengguozhu Could you try this one https://drive.google.com/file/d/0B2oZq2xVp841bkJ0ejl2RlFBLW8/view?usp=sharing |
I run the maven build successfully, and tested the SNAPSHOT distribution, the problem fixed. |
@zhengguozhu thank you very much for your time and issue report. |
OrientDB Version, operating system, or hardware.
Operating System
Expected behavior and actual behavior
Constantly wirte WARNI log: Auto transaction starting is turned off for the graph, but already started transaction is left open.Commit it manually or consider disabling auto transactions while creating the graph or its factory. [OrientGraph]
Then OrientDB halt after about 24hours.
Steps to reproduce the problem
The text was updated successfully, but these errors were encountered: