[bitnami/redis-cluster] node fail after pod restart

[angel-cdo]

Name and Version

bitnami/redis-cluster-8.3.7

What steps will reproduce the bug?

1. helm install redis-cluster my-repo/redis-cluster --version 8.3.7 --set usePassword=false --set persistence.enabled=false
2. wait for install to finish, and check that all pod are ready
3. delete one pod, which will restart it and get a new IP
4. pod will not join the cluster and will be in failed state

If I install with version 8.2.7 it will work as expected

Are you using any custom parameters or values?

--set usePassword=false --set persistence.enabled=false

What is the expected behavior?

pod should work fine after restart, just like in older versions

What do you see instead?

pod not joining the redis-cluster

Additional information

No response

[javsalgar]

Hi,

Does the issue happen when enabling the persistence? I think it has to do with the fact that the cluster state is stored in a volume.

[angel-cdo]

Hey

Thanks for the quick reply!
With persistence it does work
I know see that the reason it works with older helm chart version is because it didn't had the persistence flag
So it just doesn't work with persistence disabled

[angel-cdo]

this #13545 PR adds the option to disable persistence
But it seems that new pods created after cluster was created fail to join

[javsalgar]

@anessi did you see the issue described by @angel-cdo ?

[headlessme]

I've also just run into this issue with a cluster using persistence.enabled=false

[anessi]

I can confirm that there's an issue with the persistence.enabled=false flag. Please also see #4484 (comment) for more details.

There are the following options IMO:

• Update the scripts so that joining of an existing cluster is supported (see charts/redis-cluster disable persistence #4484 (comment))
• Remove the feature again as it does not work properly
• Add a note in the values file and mention the current restrictions that people don't run into this issue

[jotamartos]

Hi,

Thank you for your suggestions. We are going to create a task on our side to improve the initialization process when disabling the persistence in the Bitnami Redis Chart.

Sorry for the inconvenience.

[Checksumz]

I too am seeing an error when persistence.enabled=false .
I have verified that this issue is occurring since chart version 8.3.0, when the flag was introduced.

[CeliaGMqrz]

Hi, we have just updated the documentation. If you have any suggestions or questions we will be happy to provide feedback.