Update FAQ.md

2 years ago · a7cbe1e671
parent 50ff3243d5
commit a7cbe1e671
1 changed files with 3 additions and 3 deletions
--- a/DOC/FAQ.md
+++ b/DOC/FAQ.md
@ -51,12 +51,12 @@ No. While it does use SQLite as its storage engine, you must only write to the d
 Check out the [Kubernetes deployment guide](https://github.com/rqlite/rqlite/blob/master/DOC/KUBERNETES.md).

 ## Can any node execute a write request, and have the system "synchronize it all"?
-The first thing to understand is that you can send your write-request to any node in the cluster, and rqlite will do the right thing automatically. You do not need to direct your write requests specifically to the leader.
+The first thing to understand is that you can send your write-request to any node in the cluster, and rqlite will do the right thing automatically. You do not need to direct your write requests specifically to the Leader node.

-Under the covers however, only the leader can make changes to the database. If a client sends a write-request to a node and that node is not the leader, the node will transparently forward the request to the leader, wait for a response, and then return the response to the client.
+Under the covers however, only the Leader can make changes to the database. If a client sends a write-request to a node and that node is not the Leader, the node will transparently forward the request to the Leader, wait for a response, and then return the response to the client. If the node receiving the write cannot contact the Leader, the write will fail and return an error to the client.

 ## Can I send a read request to any node in the cluster?
-Yes. If a read request must be serviced by the Leader, however, rqlite will transparently forward the request to the Leader, wait for the Leader to handle it, and return the results to the client.
+Yes. If a read request must be serviced by the Leader, however, rqlite will transparently forward the request to the Leader, wait for the Leader to handle it, and return the results to the client. If the node receiving the write cannot contact the Leader, the write will fail and return an error to the client.

 ## rqlite is distributed. Does that mean it can increase SQLite performance?
 Yes, but only for reads. It does not provide any scaling for writes, since all writes must go through the leader. **rqlite is distributed primarily for replication and fault tolerance, not for peformance**. In fact write performance is reduced relative to a standalone SQLite database, because of the round-trips between nodes and the need to write to the Raft log.