# Follower Read


![left](./student-guide/diagram/03-Follower-Read-01-01.png)

------------------------------------------------------------

The reads and writes operations introduced earlier are all performed on the leader node, so this idea naturally arises. Can the follower node share the reading pressure of the leader?

The answer is yes, this function is Follower Read, and its implement method are mainly:
  - When the TiDB Server sends a read request to a follower node, the follower needs to ask the leader node in order to know the commit index of the raft log of the latest commit.
  - The leader node informs the follower node of its current commit index. If the follower finds that it has not yet applied the raft log with this sequence number, it will start waiting.
  - Until the follower confirms that the local application has been applied to the commit index sent by the leader, the follower and leader have been synchronized, and the data is read to the TiDB server at this time.

Here's a question we need to pay attention to:

In step 2 mentioned above, it is possible that the raft log sent by the leader to the follower's commit index has been appended and applied on the follower (because the leader may not have had time to apply yet, and the follower It has already been applied). At this time, there may be a phenomenon that the follower reads it first, and the leader only reads it after a while.