You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 16, 2022. It is now read-only.
When the server returns a redirect reply, it's not currently defined whether that's supposed to affect the current request type, all request types, or some subset. This could get us into trouble. For example, consider a client that was issuing Appends() as well as a Read() for an early prefix of the log. If the servers redirected Appends to a leader but old reads to a follower, the client could be bounced back and forth.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When the server returns a redirect reply, it's not currently defined whether that's supposed to affect the current request type, all request types, or some subset. This could get us into trouble. For example, consider a client that was issuing Appends() as well as a Read() for an early prefix of the log. If the servers redirected Appends to a leader but old reads to a follower, the client could be bounced back and forth.
The text was updated successfully, but these errors were encountered: