-
Notifications
You must be signed in to change notification settings - Fork 92
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
feat(redis): Make connection pool configurable [INGEST-1557] #1418
Merged
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
Currently the maximum number of connections managed by the pool is hardcoded and set to the magic number of `24` which works, but we must make sure we have a posibility to finetune this parameter. This change adds `max_connections` option into the `Cluster` config, keeps the existing `Single` config server without changes for bakwards compatibility and also introduces the `SingleOpts` variant to configure single server with additional options (with e.g. `max_connections`). The default number of redis connetions in the pool is kept to `24`. This should allow us to keep existing configs without changes and still give the posibility for finetunning connections in the future.
Since there is already configuration for few different types of the connection pools and redis clients, also most of the settings are repeatable - it is time to move all those config options if one place. Introducing `RedisConfigOptions` which will be a single place to gather all the configuration options, with sensible defaults.
* moved the redis tests into the redis crate * added serde-yaml in relay-redis crate as dev deps * keep docs properly formatted * removed the option from the config which should not be configured
jjbayer
approved these changes
Aug 16, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Re-approving, see nitpick on original PR.
jan-auer
approved these changes
Aug 17, 2022
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.
Currently the maximum number of connections managed by the pool is
hardcoded and set to the magic number of
24
which works, but we mustmake sure we have a posibility to finetune this parameter.
This change adds
max_connections
option into theCluster
config,keeps the existing
Single
config server without changes for bakwardscompatibility and also introduces the
SingleOpts
variant to configure singleserver with additional options (with e.g.
max_connections
).The default number of redis connetions in the pool is kept to
24
.This should allow us to keep existing configs without changes and still
give the posibility for finetunning connections in the future.
Also taking opportunity to refactor it a little bit .
Since there is already configuration for few different types of the
connection pools and redis clients, also most of the settings are
repeatable - it is time to move all those config options if one place.
Introducing
RedisConfigOptions
which will be a single place to gatherall the configuration options, with sensible defaults.