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

明确表达:需要如何处理的是“老主库尚未复制的写入” #323

Merged
merged 1 commit into from
Aug 14, 2023

Conversation

marvin263
Copy link

No description provided.

@yingang yingang merged commit 0794d09 into Vonng:master Aug 14, 2023
@yingang
Copy link
Collaborator

yingang commented Aug 14, 2023

谢谢!更新后应该更贴近原文的表述:

If asynchronous replication is used, the new leader may not have received all the writes from the old leader before it failed. If the former leader rejoins the cluster after a new leader has been chosen, what should happen to those writes? The new
leader may have received conflicting writes in the meantime. The most common solution is for the old leader’s unreplicated writes to simply be discarded, which may violate clients’ durability expectations.

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

Successfully merging this pull request may close these issues.

2 participants