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

Refresh connections when getting JedisMovedDataException during using pipeline #3915

Open
stillerrr opened this issue Aug 5, 2024 · 1 comment

Comments

@stillerrr
Copy link
Contributor

Expected behavior

create a JedisCluster instance and only use ClusterPipeline

the slot cache would refresh automatically when cluster node changing (Scale-out or Scale-in)

Actual behavior

the slot cache do not refresh automatically when cluster node changing (Scale-out or Scale-in)

Steps to reproduce:

  1. create a JedisCluster instance and only use ClusterPipeline
  2. Scale-out or scale-in cluster
  3. some responses would get JedisMovedDataException

Redis / Jedis Configuration

Jedis version:

Redis version:

Java version:

@stillerrr
Copy link
Contributor Author

the root cause for this is that when pipeline do not refresh slot cache when getting JedisMovedDataException

I submit a pr for this: #3699

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

No branches or pull requests

1 participant