[go: nahoru, domu]

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

All nodes detected as replicas #39

Open
quintonparker opened this issue Jul 11, 2023 · 1 comment
Open

All nodes detected as replicas #39

quintonparker opened this issue Jul 11, 2023 · 1 comment

Comments

@quintonparker
Copy link

See sheet https://docs.google.com/spreadsheets/d/1sx-wKfHocVInDt3VnxQc4BLxWzPkKqtJD0og48-ob1A/edit?usp=sharing

For prod database, node prod-002 is clearly the master as judged by metrics such as cache hits etc. and importantly replication lag is 0 which is the giveaway

This in turn throws off redis2re which then proceeds to size this database with 2x micro shards when instead it should be 4x HT shards

Copy link
Collaborator

Usually this events makes the script fail and the solution is to manually define the master node and run it again. Looks like we can use some of this information to automatically fix the issue, but still not sure if we should.

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

2 participants