# Follower Read Zone Imbalance

## Question

Does connection distribution plus nearest-replica follower read create a
zone-local TiKV read hotspot?

## Enter When

Use for read traffic or CPU concentrated in one zone while follower read is
enabled, especially with uneven TiDB/load-balancer connections by zone.

## First Batch

1. Compare TiDB connection/request distribution by zone and instance.
2. Align TiKV read traffic, CPU, and hot-read regions by zone.
3. Verify follower-read/replica selection and available PD hot-read scheduling
   behavior.

## Decision

Zone-local TiKV load alone does not prove follower-read imbalance. Require the
connection-to-replica path or equivalent label mapping. Keep load-balancer
distribution and data/leader placement as independent alternatives.

## Strongest Alternative And Stop

Check whether uneven data/leader placement explains the same read traffic
without connection skew. Stop after the connection, replica, and read-load
chain is aligned or the exact zone mapping is unavailable.