Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Apicurio registry sql connections number #4757

Closed
Prop4et opened this issue Jun 10, 2024 · 1 comment
Closed

Apicurio registry sql connections number #4757

Prop4et opened this issue Jun 10, 2024 · 1 comment
Labels

Comments

@Prop4et
Copy link

Prop4et commented Jun 10, 2024

I created a deployment on kubernetes that uses the apicurio registry sql image to create the registry. It uses an underlying postgre db and i noticed that it opens around 22 connections towards the DB. I was wondering why is that and if it's possible to limit the number of these connections. Thank you.

@carlesarnal carlesarnal moved this to Backlog in Registry 3.0 Sep 26, 2024
@carlesarnal carlesarnal added 3.x type/enhancement New feature or request labels Sep 26, 2024
@carlesarnal
Copy link
Member

Sorry, I'm way behind on my GH email. Yes, it can be configured. It's set to 20 as the initial size, and by default it has a maximum of 100. You can configure it using the property apicurio.datasource.jdbc.initial-size or it's env var equivalent, APICRUI_DATASOURCE_JDBC_INITIAL_SIZE.

@Apicurio Apicurio locked and limited conversation to collaborators Sep 26, 2024
@carlesarnal carlesarnal converted this issue into discussion #5258 Sep 26, 2024
@github-project-automation github-project-automation bot moved this from Backlog to Done in Registry 3.0 Sep 26, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
Projects
Status: Done
Development

No branches or pull requests

2 participants