You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Two redis clusters must work seamless if they have different namespace and name. accordign to this question
What do you want to achieve?
Run Mulltiple redis clusters in different namespaces with single operator
Actual behaviour
The replicas from cluster/replicated setup have connected to master of another cluster in diffrent namespace.
Describe step by step what you've have done to get to this point
They were working fine from last two months but yesterday at 6am, spot nodes in which these replicas are running have been taken down by GCP and new ones have spinned off during this transition soemthing happened which resulted in sudden drop to 2000+ keys and interconnection of replicas between clusters.
Environment
kubernetes
Redis Operator version v1.2.4
Kubernetes version 1.26
Kubernetes configuration used (eg: Is RBAC active?)
The text was updated successfully, but these errors were encountered:
My redis failover cluster are names as sync-redis and aurora-redis.
In the below logs we can see replicas of sync-redis are made slaves of master of aurora-redis.
Expected behaviour
Two redis clusters must work seamless if they have different namespace and name. accordign to this question
What do you want to achieve?
Run Mulltiple redis clusters in different namespaces with single operator
Actual behaviour
The replicas from cluster/replicated setup have connected to master of another cluster in diffrent namespace.
Describe step by step what you've have done to get to this point
They were working fine from last two months but yesterday at 6am, spot nodes in which these replicas are running have been taken down by GCP and new ones have spinned off during this transition soemthing happened which resulted in sudden drop to 2000+ keys and interconnection of replicas between clusters.
Environment
kubernetes
The text was updated successfully, but these errors were encountered: