# Read Data: Follower Read
__*Follower Read*__

![left](./student-guide/diagram/FollowerRead_aa_001_2022051.png)

------------------------------------------------------------
The reads and writes operations introduced earlier are all performed on the leader node, so this naturally led to the idea that the follower node can share the reading pressure of the leader?

The answer is yes. This function is Follower Read. The main method implement it is:

1. When the TiDB Server sends a read request to a follower node, the follower needs to ask the leader node for the order number (commit index) of the raft log of the current latest commit.

2. The Leader node informs the follower node of the current commit index. If the follower finds that it does not have a raft log with the sequence number applied, it will start waiting.

3. Until the follower confirms that it has applied locally to the commit index just sent by the leader, the follower and leader are synchronized, and the data is read to the TiDB Server.

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

In step 2 mentioned above, it is possible that the raft log of the commit index sent by the leader to the follower has been appended and applied on the follower (because the leader may not have had time to apply, and the follower (Already applied), at this time, it is possible that the follower reads it first, and the leader only reads it after a while.