We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Submitted by: @dyemanov
Under a concurrent load when many EXECUTE STATEMENTs are running, the engine threads may deadlock, thus denying any service for the attached database.
The issue seems to be caused by a inconsistent mutex locking order.
Commits: 738a3cd
The text was updated successfully, but these errors were encountered:
assignee: Dmitry Yemanov [ dimitr ]
Sorry, something went wrong.
status: Open [ 1 ] => In Progress [ 3 ]
status: In Progress [ 3 ] => Open [ 1 ]
assignee: Dmitry Yemanov [ dimitr ] => Vlad Khorsun [ hvlad ]
status: In Progress [ 3 ] => Resolved [ 5 ]
resolution: Fixed [ 1 ]
Fix Version: 2.5 RC1 [ 10362 ]
status: Resolved [ 5 ] => Closed [ 6 ]
QA Status: No test
status: Closed [ 6 ] => Closed [ 6 ]
QA Status: No test => Not enough information
hvlad
No branches or pull requests
Submitted by: @dyemanov
Under a concurrent load when many EXECUTE STATEMENTs are running, the engine threads may deadlock, thus denying any service for the attached database.
The issue seems to be caused by a inconsistent mutex locking order.
Commits: 738a3cd
The text was updated successfully, but these errors were encountered: