jdbc_static filter: configure connection pool #187
Merged
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.
By increasing the size of the connection pool from the Sequel-default 4 to 16, we increase the max parallelism of pipelines that are using this filter by four- fold, reducing the situations where a pipeline's total throughput is constrained by this plugin's connection pool to the internal Derby DB.
We also increase the pool timeout from the Sequel-default 5 seconds to 30 seconds, so that failures to immediately acquire a connection don't result in failed lookups.
This issue is meant to mitigate the root-cause beneath #186 without expanding the scope of configuration options for the
jdbc_static
filter, which would be a substantial effort.