Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[BUG-python/deployment] Server crashes when deployed with K8s and postgres (connection pooling issue) #5819

Open
Kop3sh opened this issue Mar 2, 2025 · 0 comments · May be fixed by #5820
Open

[BUG-python/deployment] Server crashes when deployed with K8s and postgres (connection pooling issue) #5819

Kop3sh opened this issue Mar 2, 2025 · 0 comments · May be fixed by #5820

Comments

@Kop3sh
Copy link

Kop3sh commented Mar 2, 2025

Describe the bug

In this case Agilla server crashes even under minimal concurrent load and returns server errors (500 error codes)

It turns out the issue is related to postgres having PgBouncer connection pooling extension which has compatibility issues with SQLAlechemy's QueuePool class (default pooling class)

references

similar reports

Stacktrace and code to create the bug

No response

Expected behavior

No response

Environment

current deployment stack is using K8s and PostgreSQL + PgBouncer

Additional context

No response
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(db): add poolclass config in SQLAlchemy engine for compatabilty with PgBouncer Kop3sh/argilla
1 participant
@Kop3sh