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

ClusterConnections do not close dedicated ClusterCommandExecutor instances [DATAREDIS-637] #1216

Closed
spring-projects-issues opened this issue Apr 28, 2017 · 0 comments

Comments

@spring-projects-issues
Copy link

@spring-projects-issues spring-projects-issues commented Apr 28, 2017

Mark Paluch opened DATAREDIS-637 and commented

Instances of JedisClusterConnection and LettuceClusterConnection created without a shared ClusterCommandExecutor create their own ClusterCommandExecutor instance but do not perform a cleanup after closing the connection


Affects: 1.7.5 (Hopper SR5)

Backported to: 1.8.4 (Ingalls SR4), 1.7.11 (Hopper SR11)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants