HSEARCH-5045 Raise various default max-connection config properties for the Elasticsearch backend #4347
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I wonder whether it would make sense to make the total max connections some high number (e.g. |
Seems to me this could lead to problems with large Elasticsearch cluster? I.e. with a 20-node cluster, one app instance could end up opening 400 connections... |
|
good point! 😃 thanks! |
|
marko-bekhta
force-pushed
the
feat/HSEARCH-5045-Raise-default-max-connection-per-route-for-the-Elasticsearch-backend
branch
from
58bec65
to
dbb8afd
Compare
…or the Elasticsearch backend
marko-bekhta
force-pushed
the
feat/HSEARCH-5045-Raise-default-max-connection-per-route-for-the-Elasticsearch-backend
branch
from
dbb8afd
to
7070d2d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://hibernate.atlassian.net/browse/HSEARCH-5045
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license
and can be relicensed under the terms of the LGPL v2.1 license in the future at the maintainers' discretion.
For more information on licensing, please check here.