Skip to content
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

Two different redis clusters in different namespaces interconnected. Production disturbed. #698

Open
PrudhviApx7 opened this issue May 16, 2024 · 1 comment

Comments

@PrudhviApx7
Copy link

PrudhviApx7 commented May 16, 2024

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

  • Redis Operator version v1.2.4
  • Kubernetes version 1.26
  • Kubernetes configuration used (eg: Is RBAC active?)
@PrudhviApx7
Copy link
Author

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.
Screenshot from 2024-05-16 21-35-04
Screenshot from 2024-05-16 21-36-25

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant