We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
文章中提到,在無主跟多主的情況下,大多或使用最後寫入勝利的策略,但還是會有問題,其中一個提到:
LWW 無法區分 高頻順序寫入中,客戶端 B 的增量操作 一定 發生在客戶端 A 的寫入之後)和 真正併發寫入(寫入者意識不到其他寫入者)。需要額外的因果關係跟蹤機制(例如版本向量),以防止違背因果關係。
想問有人有實做過因果關係跟跟蹤機制的經驗嗎?
The text was updated successfully, but these errors were encountered:
Sorry, something went wrong.
AK4codee
No branches or pull requests
文章中提到,在無主跟多主的情況下,大多或使用最後寫入勝利的策略,但還是會有問題,其中一個提到:
想問有人有實做過因果關係跟跟蹤機制的經驗嗎?
The text was updated successfully, but these errors were encountered: