Closed sentry-io[bot] closed 5 months ago
The error probably's happening because of this insert stement doesn't have a database error handling.
The hypothesis behind this is as follows: During benchmarking, the database receives more connections than it can handle due to the high volume of requests. As a result, it throws this error when attempting to update a user, acquiring a connection that hasn't been rolled back, which consequently causes PendingRollbackError in consequent requests in the same server workers.
2 quick things that could help:
Updating pool size instead of maximum number of db connections might be a better point to start with.
Was resolved after (#145) was merged
Sentry Issue: CELLARIUM-CLOUD-1K