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

Introduce new config attribute for Puma #378

Conversation

iaftab-alam
Copy link
Contributor

Currently, with Puma, all processes (i.e. main + Puma workers) is configured with the same cc db max_connections. This PR aims to introduce new config attribute (max_db_connections_per_process / optional). If not specified, the default db max_connections from cc_ng will be used.

  • A short explanation of the proposed change:

  • An explanation of the use cases your change solves

  • Links to any other associated PRs

  • I have viewed signed and have submitted the Contributor License Agreement

  • I have made this pull request to the develop branch

  • I have run CF Acceptance Tests on bosh lite

Currently, with Puma, all processes (i.e. main + Puma workers) is configured with the same cc db max_connections.
This PR aims to introduce new config attribute (max_db_connections_per_process / optional).
If not specified, the default db max_connections from cc_ng will be used.
Copy link
Contributor

@johha johha left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm 👍

@johha johha merged commit 46e642c into cloudfoundry:develop Jan 25, 2024
2 checks passed
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

Successfully merging this pull request may close these issues.

2 participants