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

EVA-3713 Adding Hikari max pool size connection property configuration #60

Merged
merged 2 commits into from
Nov 15, 2024

Conversation

nitin-ebi
Copy link
Contributor

No description provided.

@nitin-ebi nitin-ebi self-assigned this Nov 14, 2024
Copy link
Member

@tcezard tcezard left a comment

Choose a reason for hiding this comment

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

I might have missed something but why are we not changing the _common_eva_pipeline_properties to only use one connection ?

@nitin-ebi
Copy link
Contributor Author

I might have missed something but why are we not changing the _common_eva_pipeline_properties to only use one connection ?

As discussed in the standup, eva-pipeline uses 1 connection by default and if it tries to use more than 1, it will be restricted to 2 with the settings.

@nitin-ebi nitin-ebi merged commit 2484eeb into EBIvariation:master Nov 15, 2024
3 of 4 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.

3 participants