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
arbitrary stuck queries #827
Comments
Facing same issue |
Hi @Miraj98, thanks for responding. Do you have any hints where and when you are facing this problem? maybe also @porsager has some hints for us, where we should look at to find something? |
Hey @JuHwon I just did some debugging and I am facing connection issues specifically when using bun so not sure if my case will help. Sorry. |
i would not exclude the possibility that the issue is related when the only difference is using bun vs node, right? |
TLDR: In depth: P.S I have an assumption the the connection pool has an issue when too many concurrent transactions are done currently and that's why you had this issue while doing |
Would you think your descriptions matches the ones in #738 ? That change has been released in v3.4.4 today. Would be nice if you all could give that a try and report back. |
We have an issue, where the sql client just does not respond. In other words, the promise does not resolve nor reject.
The application has peaks with lots of concurrent requests. The issue though also happens when there is not much load. It just arbitrary does not respond. When i restart the application, everything works fine again.
The client configuration:
I have a feeling that it happens after the service ran for some time already.
I also had a feeling that it often occurs with
sql.begin(...)
, but i have also seen it once at a singlesql`SELECT * FROM x WHERE id = ${id}`
Not sure where to start looking at here, since we are currently not able to reproduce it. Does anyone have any ideas why this could happen? I would also be happy to contribute to the project if we are able to find the issue here.
UPDATE
Here is the chart of one occurrence of the postgres DB, the needle is placed when the incident happened.
The text was updated successfully, but these errors were encountered: