Tracking issue for linearizable read

[drmingdrmer]

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).

• Requirement discussion: Feature request: optimization for read-only requests #262
  • Linearizable read with ReadIndex #965
• Support consistent read with leader lease #804
• Support consistent read with log-id #805

[github-actions]

👋 Thanks for opening this issue!

Get help or engage by:

• /help : to print help messages.
• /assignme : to assign this issue to you.

[HHoflittlefish777]

@drmingdrmer Can I try it?

[drmingdrmer]

@HHoflittlefish777

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

[HHoflittlefish777]

@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.
Wish everything goes well.