-
Notifications
You must be signed in to change notification settings - Fork 40.4k
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
RedisReactiveHealthIndicator is broken with Redis cluster mode #22061
Comments
@wilkinsona Here is the separate issue you asked for in #21514 |
Thanks for the report and the sample application. I can reproduce the problem with the provided sample and instructions. The root cause is a change made to Spring Data Redis This seems to me like a condition that Spring Boot will need to handle, but I'm not sure how Boot should figure out what's going on or if there's something more Spring Data Redis should be doing to simplify the situation. cc @mp911de |
We changed the behavior as bugfix but weren't aware that the reactive health check would fail. I suggest issuing a |
After upgrading to Spring Boot 2.2.8.RELEASE from 2.2.7.RELEASE, the Redis health indicator started reporting down with the following error detail on clustered Redis:
It appears that the info properties coming back in 2.2.8 have the IP address and port prefix on the keys (e.g.
127.0.0.1:7002.redis_version
). It also appears the properties come back from each node this way.The attached zip file reproduces the issue. Instructions can be found in
instructions.md
in the attached zip for how we are starting a clustered Redis docker container.clustered-redis-issue.zip
The text was updated successfully, but these errors were encountered: