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.

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

[Suggestion] - Configure Database Connection Pool via values.yml #863

Open
1 task done
nagarajuvemula789 opened this issue Aug 14, 2024 · 1 comment
Open
1 task done

Comments

@nagarajuvemula789
Copy link

Suggestion

Background

To provide better flexibility and configurability for Jira Data Center deployments on Kubernetes, it would be beneficial to allow users to specify database connection pool sizes directly from the values.yml file.

Proposed Change

I suggest updating the dbconfig.xml template within the Helm chart to dynamically populate the <pool-min-size> and <pool-max-size> values using the values provided in values.yml.

Changes in values.yml

Add the following entries in values.yml:

database:
connectionPool:
minSize: 20 # Minimum pool size
maxSize: 100 # Maximum pool size
maxIdle: 50 # (Optional) Maximum idle connections
maxWait: 30000 # (Optional) Maximum wait time in ms

Product

Jira

Code of Conduct

  • I agree to follow this project's Code of Conduct
@bianchi2
Copy link
Collaborator

bianchi2 commented Aug 15, 2024

@nagarajuvemula789 while your suggestion makes sense, there's a way to override the default database settings:

jira:
  additionalEnvironmentVariables:
  - name: ATL_DB_POOLMAXSIZE
    value: "200"

and so on...
You will find the complete list of available env vars at https://atlassian.github.io/data-center-helm-charts/containers/JIRA/#optional-database-settings

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants