-
Notifications
You must be signed in to change notification settings - Fork 9.8k
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
ReadIndex may read stale value #7331
Comments
/cc @xiang90 @swingbach |
xiang90
added a commit
that referenced
this issue
Feb 17, 2017
raft: fix read index request for #7331
Fixed by #7332 |
gyuho
pushed a commit
that referenced
this issue
Feb 22, 2017
gyuho
pushed a commit
that referenced
this issue
Feb 22, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When trying to use read index with safe option, raft node will choose the committed index as the index to be read. However this may not be correct when leadership is changed. New leader's committed index may not be the cluster's actual committed index until an empty entry is committed. During this period, new leader's committed index may be small than the old leader's. If read_index request is handled, it may read an old index which contains stale values.
cc @siddontang
The text was updated successfully, but these errors were encountered: