Skip to content
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

Closed
BusyJay opened this issue Feb 15, 2017 · 2 comments
Closed

ReadIndex may read stale value #7331

BusyJay opened this issue Feb 15, 2017 · 2 comments

Comments

@BusyJay
Copy link
Contributor

BusyJay commented Feb 15, 2017

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

@siddontang
Copy link
Contributor

/cc @xiang90 @swingbach

@xiang90
Copy link
Contributor

xiang90 commented Feb 17, 2017

Fixed by #7332

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants