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.

Sign up for GitHub

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

Jump to bottom

6th Draft Multimaster Edit Document #29

Open

BobEQAlpha opened this issue Sep 13, 2021 · 3 comments

Contributor

BobEQAlpha commented Sep 13, 2021 •

edited

Loading

From Slack Community :

Advanced Configuration: Rewrite Replica Quorum / Replica-serve-stale-data

Provide more low-level detail

Investigate on failover between active replication and multi-master : https://community.keydb.dev/t/read-only-active-replicas/164/3
Slack community

Contributor Author

BobEQAlpha commented Nov 8, 2021 •

edited

Loading

Create a section that a RDB save is performed first when sync'ing. Add the implications of this such as transfer storms and how it might be better to use a ring versus a mesh topology.

Contributor Author

BobEQAlpha commented Nov 8, 2021

https://community.keydb.dev/t/active-replication/44
A ring topology will reduce the amount of bandwidth used communicating between your cluster, at the expense of slightly higher latency before each node is updated.

Contributor Author

BobEQAlpha commented Nov 18, 2021

I see the docs suggest that a multimaster setup may only be useful for a ‘hot standby’. But that doesn’t make much sense

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment