-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Stale read when using read_index request #9351
Comments
Since 4.0.8, tiflash won't use ReadIndex to get read-index from leader directly. |
I remember there is a solution to use proxy to do reading across DC, which also use read index. @hicqu Is it still a valid solution? Is the stale read proposal a good alternative to it? |
@BusyJay that solution is paused and I think the stale read proposal is more useful than that. Is it necessary to fix the bug for |
The only way to fix for them is using a hotfix. I suggest to ask them to upgrade to v4.0.9 instead. |
Can it be closed now? |
Why? The API still exists and it can return wrong result. |
Bug Report
Similar to #9208, ReadIndex request can be given a stale index after just transferring leader. The API doesn't seem to be used anymore, so the best way to solve it is removing the API completely.
@NingLin-P @gengliqi PTAL
/cc @solotzg, just make sure tiflash will not use the API in the future.
The text was updated successfully, but these errors were encountered: