You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, the Surefire shutdown times out due to heavy connection cleanup via the shutdown hooks. In a regular test run, we retain about 2000 open Redis connections. The cleanup requires a significant amount of time.
We should:
Reuse pooled connections as much as possible (LettuceReactiveCommandsTestSupport causes a lot of connections)
Revisit our method source caching to cache input parameters. right now, we create fixtures (and therefor pools) for each method via @ParameterizedRedisTest
Release resources via method source retrieval to close resources early on
Reuse shared ClientResources
Use SimpleAsyncTaskExecutor as default utility in ClusterCommandExecutor
The text was updated successfully, but these errors were encountered:
Delegate RedisClientProvider.getClient() across connection providers. Use SimpleAsyncTaskExecutor as default in ClusterCommandExecutor to avoid ThreadPoolTaskExecutor pollution.
See #2575
Delegate RedisClientProvider.getClient() across connection providers. Use SimpleAsyncTaskExecutor as default in ClusterCommandExecutor to avoid ThreadPoolTaskExecutor pollution.
See #2575
Reuse condition objects in command and version condition extensions.
Shut down ClientResources via ShutdownQueue and ensure shared client resources usage.
Add close support to our MethodArgumentsProvider. Reuse LettuceTestClientConfiguration for test client config settings.
Closes#2575
Right now, the Surefire shutdown times out due to heavy connection cleanup via the shutdown hooks. In a regular test run, we retain about 2000 open Redis connections. The cleanup requires a significant amount of time.
We should:
LettuceReactiveCommandsTestSupport
causes a lot of connections)@ParameterizedRedisTest
ClientResources
SimpleAsyncTaskExecutor
as default utility inClusterCommandExecutor
The text was updated successfully, but these errors were encountered: