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

第九章:2PC vs 共識演算法 (Zab, Raft) - Kyle #103

Open
kylemocode opened this issue Aug 9, 2022 · 1 comment
Open

第九章:2PC vs 共識演算法 (Zab, Raft) - Kyle #103

kylemocode opened this issue Aug 9, 2022 · 1 comment
Labels
question Further information is requested

Comments

@kylemocode
Copy link
Collaborator

文章中提到「透過對 2PC 的學習,我們將繼續努力實現更好的一致性演算法,比如 ZooKeeper(Zab)和 etcd(Raft)中使用的演算法」,想問現實在開發上是不是比較少會選擇像是 2PC + XA 協議的方式來處理分散式共識問題(因為效能關係:資料庫隔離層級需要改成 Serializable 級別 or 文章提及的協調者故障或失效的話參與者只能等待的不確定狀態)?

又想問各位在實際開發中會不會盡量避免處理分散式的共識問題?有的話是採用哪種方式?(目前有聽到的可能 ZooKeeper 居多)

@kylemocode kylemocode added the question Further information is requested label Aug 9, 2022
@kylemocode kylemocode changed the title 第九章:2PC vs 一致性演算法 (Zab, Raft) 第九章:2PC vs 共識演算法 (Zab, Raft) - Kyle Aug 9, 2022
@Parkerhiphop
Copy link

Parkerhiphop commented Aug 10, 2022

Zookeeper 就是用來處理時間。
資料擷取照著某時間點往下拉,勁量讓每個 Worker 拉到正確的時間段。
Zookeeper 用 squential consistency 來確保不會拉到舊的。

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

No branches or pull requests

2 participants