-
Notifications
You must be signed in to change notification settings - Fork 143
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
Tracking issue for linearizable read #806
Comments
👋 Thanks for opening this issue! Get help or engage by:
|
@drmingdrmer Can I try it? |
Thank you for your interest in contributing to this feature. However, we are not ready to implement it at this time due to several refactoring tasks that need to be completed first, including updating the leader lease: leader lease is not updated by leader itself, only by followers. I will contact you when the dependency is ready, and if you are still interested, we can discuss further. Please let me know if you require additional information. Best regards |
@drmingdrmer Thanks for you reply.I am willing to wait until refactor completed.I don't need additional information at the moment. In the period,I would like to try some simple task to familiarize openraft. Is some suitable task I can do?If not, it is no matter. |
In a distributed system, a read request should see the result of a former succeeded write, by wall-clock means, or by pseudo time(log id) means.
To ensure consistency in a distributed system, when a read request is made, it should be able to access the outcome of a previously successful write, either through wall-clock means or by using pseudo time (log id).
ReadIndex
#965The text was updated successfully, but these errors were encountered: