Add configuration to enable Redis Cluster topology refresh
See original GitHub issueRedis Cluster can be reconfigured at runtime and Redis clients should to pick up these changes to stay operable. Updating the topology is a specialized topic on its own as Redis Cluster does not push changes to the client but rather clients need to poll topology changes.
Automated (background) topology refresh is currently supported only by Lettuce via ClusterClientOptions and a nested ClusterTopologyRefreshOptions object.
Jedis does not support background topology refreshing.
It would make sense to provide some means to configure cluster topology refresh. The way how Lettuce topology updating is configured (setting ClusterClientOptions via LettuceClientConfigurationBuilder) might contradict with LettuceClientConfigurationBuilderCustomizer.
What do you think?
See also:
Issue Analytics
- State:
- Created 5 years ago
- Comments:12 (7 by maintainers)
Top Related StackOverflow Question
@mp911de @wilkinsona Do you any plan for including this feature in a new release? I’d really appreciate it if the topology refresh feature could be supported by spring boot, so that my RedisTemplate related code does not need to be re-written~
@superbool new features are not added to maintenance releases.
2.3.xis in maintenance as well in the meantime so please upgrade to that.