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
In principle it's possible to have a node re-route a HTTP request to the leader node, if a follower receives it. Right now that is not the chosen behavior, and the follower node returns with HTTP 301. This provides maximum transparency to clients, allowing them to talk directly to the leader and be sure that a command has been accepted.
The text was updated successfully, but these errors were encountered:
It should be noted that adding this feature introduces a lot of possible error cases, that need to be handled with timeouts. Not ruling it out, but it must be considered carefully before allowing it. At the very least, it must able to be disabled by the client if it chooses.
In principle it's possible to have a node re-route a HTTP request to the leader node, if a follower receives it. Right now that is not the chosen behavior, and the follower node returns with HTTP 301. This provides maximum transparency to clients, allowing them to talk directly to the leader and be sure that a command has been accepted.
The text was updated successfully, but these errors were encountered: