-
Notifications
You must be signed in to change notification settings - Fork 267
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
FSM log entries are applied lazily #90
Comments
Ticketd will wait the raft_msg_entry_response_committed return 1. It means the __raft_applylog function has been called. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This might be considered a issue or simply a design choice, but the fact
raft_recv_appendentries_response
does not invokeraft_apply_all
after updating the commit index and rather relies on the next call ofraft_periodic
to do that, means that a client call toraft_msg_entry_response_committed
might return 1 even if the FSM hasn't yet applied the log entry.It feels this might cause confusion to users or timing-related issues, see for example the scenario I described in issue #12 of ticketd.
Please let me know if my reading is correct. Thanks!
The text was updated successfully, but these errors were encountered: