-
-
Notifications
You must be signed in to change notification settings - Fork 547
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
postgresql deadlock #608
Comments
I'm not exactly sure what you mean with the steps to reproduce. If you are executing manually:
|
yes, in the case of postgresql deadlocking, chirpstack-application-server will be crash , it will prompt "pq:sorry,already too many clients".so i want to know how to resolve this question? thank you ! |
I'm open for fixes, but I would recommend looking into migrating to ChirpStack v4. The v4 architecture is a lot simpler as you do not have to deal with multiple databases. It is also the place where all the new development is happening :-) |
I'm so appreciate for you reply.For some reason, i can't upgrade the version to Chirpstack V4, so i hope you can give good news about the question as soon as possible ,thanks so much! |
The logs: |
We are facing the same problem, any update on this? |
What happened?
when user subscribe the query devices by DevEUI, the postgresql make the deadlock. for this reason , the chirpstack_as crashed!
What did you expect?
postgresql can be unlock in the case of high concurrency.
Steps to reproduce this issue
Steps:
Could you share your log output?
Your Environment
The text was updated successfully, but these errors were encountered: