charts icon indicating copy to clipboard operation
charts copied to clipboard

redis pod are continuosly restarting

Open abhishekGupta2205 opened this issue 3 years ago • 10 comments

Name and Version

bitnami, redis

What steps will reproduce the bug?

helm install redis redis

Are you using any custom parameters or values?

architecture=replication 1 master + 2 slave architecture sentinels =enabled

What is the expected behavior?

redis pods should run fine without any restarts

What do you see instead?

redis pods are restarting automatically without any error in logs.

Additional information

Screenshot from 2022-08-02 15-30-37 Screenshot from 2022-08-02 15-30-23 Screenshot from 2022-08-02 15-30-12 Screenshot from 2022-08-02 15-30-02

abhishekGupta2205 avatar Aug 02 '22 10:08 abhishekGupta2205

these are the logs of redis master pod

abhishekGupta2205 avatar Aug 02 '22 10:08 abhishekGupta2205

Screenshot from 2022-08-02 15-32-33

abhishekGupta2205 avatar Aug 02 '22 10:08 abhishekGupta2205

Screenshot from 2022-08-02 15-37-38

abhishekGupta2205 avatar Aug 02 '22 10:08 abhishekGupta2205

due to this restart process sentinels are changing the master , which is craeting a problem i cant find any cause for these restarts in the logs

abhishekGupta2205 avatar Aug 02 '22 10:08 abhishekGupta2205

Hi @abhishekgupta2205,

Can you please share what version of the bitnami/redis chart are you using?

The bitnami/redis have recently received some changes that should fix this issue.

If possible, please update to the latest version and let me know if the issue persists?

To update to the latest version, run helm repo update and run helm search repo redis, at this moment, latest version is 17.0.6:

$ helm repo update
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "bitnami" chart repository
Update Complete. ⎈Happy Helming!⎈
$ helm search repo redis
NAME                 	CHART VERSION	APP VERSION	DESCRIPTION
bitnami/redis        	17.0.6       	7.0.4      	Redis(R) is an open source, advanced key-value ...
bitnami/redis-cluster	8.1.2        	7.0.4      	Redis(R) is an open source, scalable, distribut...

migruiz4 avatar Aug 03 '22 08:08 migruiz4

redis-16.4.0 Can you tell me some reason why it is happening

abhishekGupta2205 avatar Aug 03 '22 11:08 abhishekGupta2205

Can you tell me some reason why it is happening The pod liveness/readiness probes are failing repeatedly, causing the pod to restart.

redis-16.4.0

Version 16.4.0 was released 6 months ago, and during that time the bitnami/redis chart have received several fixes and improvements. In order to help help you, we need you to use a recent version of the chart, otherwise, it is difficult to determine if it is a bug that has already been addressed, a configuration error, or a bug existing in the latest version of the chart. In addition, if a fix were applied, you would need to upgrade to the latest version to benefit from it.

migruiz4 avatar Aug 03 '22 13:08 migruiz4

actuall i have already deployed and traffic is comijng on it. so it is not possible to change the helm chart version . it will be really helpful if you can provide any solution or info about any previous bugs related to it

abhishekGupta2205 avatar Aug 03 '22 18:08 abhishekGupta2205

@migruiz4 can you give any other suggestion?

abhishekGupta2205 avatar Aug 05 '22 06:08 abhishekGupta2205

Hi @abhishekgupta2205,

actuall i have already deployed and traffic is comijng on it. so it is not possible to change the helm chart version .

The version of the Redis Cluster can be upgraded by using the command helm upgrade.

I would suggest troubleshooting why the livenessProbe is timing out (and restarting the pod), you can log into the pod and run the redis-cli command manually.

migruiz4 avatar Aug 05 '22 15:08 migruiz4

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

github-actions[bot] avatar Aug 21 '22 01:08 github-actions[bot]

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.

bitnami-bot avatar Aug 26 '22 01:08 bitnami-bot