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

Different RedisFailover's sentinels join together #6

Open
dbackeus opened this issue Nov 12, 2024 · 0 comments
Open

Different RedisFailover's sentinels join together #6

dbackeus opened this issue Nov 12, 2024 · 0 comments

Comments

@dbackeus
Copy link

dbackeus commented Nov 12, 2024

I'm reopening what was probably the most critical bug before the fork: spotahome#550

It can result in complete data loss for a cluster. Not just in theory, it happened in our production k8s cluster. Eg. if cluster A gets mixed up with cluster B and cluster A ends up being elected master for all nodes, the previously existing data of cluster B will get completely overwritten by cluster A's.

I still believe the appropriate solution is to start relying on hostnames instead of injecting pod IP's into config as mentioned in spotahome#550 (comment)

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