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
Lowering the JDBC pooled connections to 192 haven't resolved the problem. Next steps to try:
But how the code manages to make 200+ waiting writing transactions with 192 connections?
The text was updated successfully, but these errors were encountered:
The mystery is no mystery anymore: I've missed the fact that there IS really a transaction deadlocks. See PR №5239 in the parent repository.
So sorting by id should be added for the update statements.
id
Sorry, something went wrong.
No branches or pull requests
Lowering the JDBC pooled connections to 192 haven't resolved the problem. Next steps to try:
Lower the thread count in the worker pool;Lower the pooled connections value;But how the code manages to make 200+ waiting writing transactions with 192 connections?
The text was updated successfully, but these errors were encountered: