Closed jonathon2nd closed 1 year ago
@abhishekgupta2205 because in sentinel deployment you connect your application to sentinels (through a service) directly, and the redis client should be setinel-aware (java has those, jedis for example) then even if master changes the app can switch because sentinels will tell it to do so
@abhishekgupta2205 because in sentinel deployment you connect your application to sentinels (through a service) directly, and the redis client should be setinel-aware (java has those, jedis for example) then even if master changes the app can switch because sentinels will tell it to do so
I apologize for not testing this yet with a Spring Boot app and asking this anyway, but the question for me is this: after applying useHostnames=false, can I still not know about specific IPs when connecting to sentinel from another application (and continue to use the headless service hostnames)?
@abhishekgupta2205 you dont connect to sentinel via ip, there is a sentinel service created
@gediminasmorkys i want that only that after applying hostaname=false , internat functioning may happen with pod ip but it should return some fixed svc name
@abhishekgupta2205 this is the service you want, just use the sentinel port 26379
anyways this is offtopic
Just a quick note to let you know that the changes are merged. Version 17.7.0 of the Bitnami Redis Chart will include support to use IPs instead of domains when configuring the different nodes by using the useHostnames
parameter.
Tilt is a time drift issue. Can you change the time drift tolerance and recompile redis? Aformentioned tolerance is not configurable and recompilation will be required
Just a quick note to let you know that https://github.com/bitnami/charts/pull/14599. Version 17.7.0 of the Bitnami Redis Chart will include support to use IPs instead of domains when configuring the different nodes by using the useHostnames parameter.
Hey jotamartos :wave: thx for that hint. But the version 17.7.0
is not yet released (successfully), right? We get an error, when trying to deploy that chart version.
Hi @mszumilak,
We do not modify the source code of the components we build. If this is a problem in the Redis' source code, the developers should update that parameter or provide a way to modify that value using a compilation option.
@ChrisNoSim Regarding version 17.7.0, we noticed it was not published properly. We are working on it and expect to have an updated version soon. Will ping you when it's available.
Hi @ChrisNoSim,
Bitnami Redis chart is now updated with these changes. The latest available version is 17.7.1
$ helm search repo bitnami/redis
NAME CHART VERSION APP VERSION DESCRIPTION
bitnami/redis 17.7.1 7.0.8 Redis(R) is an open source, advanced key-value ...
Thanks for fixing this issue. We've had the tilting issue for a long while and with 17.7.0 this was the first weekend without any restarts.
@PovilasKM did you use the new useHostnames parameter and set it to false?
Thanks for updating the REDIS chart.
We set the useHostnames
to false
on Friday and since then we have not seen the tilt mode in this cluster. We will roll out that setting to our other REDIS clusters and lets see. :partying_face:
I'm really glad to hear that! 😄 Thanks for letting us know
@mgrzeszczak we've used useHostnames and set it to false. Now there is no tilting in logs and no "random" restarts.
@marcosbc , after disabling use hostname feature , connectivuty of pods from differnt k8s cluster would be impacted also . as now master address would be return in form of pod ip , which is only accessible inside same cluster. how can i access redis-master pod via sentinel from a diifferent cluster .
@jotamartos , my issue is that after connecting with redis-sentinel , i need information of my redis-master in form of ip and port ( when using jedis or connecting from a java service ) . when the hostname usage is disabled , the ip which sentinel will return will be a pod ip . As you know pod ip is only connectible within same k8s cluster . but if my java service is outside the cluster where my redis server is running , my java application would not be able to connect to the pod ip . thats why we need something that is accessible irrespective of cluster .
my usage of redis --
java application --> sentinel-->(return ip of redis master to java appliction )----> redis master is connected to java application
is there any way we can address this issue also , i can get an ip and port , which are accessible from anywhere
Name and Version
bitnami/redis 16.8.2
What steps will reproduce the bug?
Install bitnami/redis in sentinel mode.
Wait a while (It typically happens within an hour) for sentinel containers to start restarting for no reason.
Are you using any custom parameters or values?
What is the expected behavior?
Expected behavior is sentinel to not restart for no seemingly reason.
What do you see instead?
After some period of time, sentinel containers enter tilt mode on and off again, and then just restart.
Entire log of sentinel container up till restart
Redis container log.
Additional information
Seems like it may be the probes killing the container?
This has also been happening for a while, we just have not noticed cause the redis container is not restarting, so all data is fine.
I think it might be host related somehow. The only reason I am thinking this is because we were testing in a multi-cluster environment. Part on-prem and the other part in a remote managed k8s. We see this behavior on-prem, and not in remote k8s.
I have been testing on a new cluster with Rocky Linux
But this is also happening on the older deployment from the image above
I am still testing, I am pairing down the values file more and more until I see the behavior stop. This is taking a while as it take a random long amount of time until sentinel enters tilt mode repeatedly and dies.
We have many things deployed onto these clusters, and have no other observed issues.
I have been poking around the hosts and trying to see if there was anything happening that would line up with the behavior explained here: https://redis.io/docs/manual/sentinel/#tilt-mode and I have not found anything yet. Metrics for the vms are all reasonable. No monitoring or alarming is going of for any of these clusters/workers.
I am unsure what is happening. If anyone reading this has any insight on what is happening, input would be greatly appreciated.
Thank you!