Every node in the cluster "knows" the network address of the Leader. It knows because a) it's part of the Raft cluster configuration, and b) every follower "hea

Every node in the cluster "knows" the network address of the Leader. It knows because a) it's part of the Raft cluster configuration, and b) every follower "heartbeats" to the Leader periodically. So it's actually pretty simple for a given node to contact the Leader. If a node receives a request which must be performed on the Leader, and that node is not itself the Leader, it can do one of the following things: 1) reject the request with an error, but this isn't really a production-viable option. 2) reject the request with an error, but tell the client where the Leader can be found, so the client can retry the request, this time sending the request to the Leader. 3) transparently forward the request to the leader, wait for the Leader to execute the request, get the response, and return the response to the client. In this case the client doesn't even know the forwarding to the Leader happened. rqlite supports mode 2 and 3, client can choose which behavior it wants, on a request-by-request basis. Option 3 is the default. https://github.com/rqlite/rqlite/blob/master/DOC/DATA_API.md#how-rqlite-handles-requests https://github.com/rqlite/rqlite/blob/master/DOC/DATA_API.md...