reference: update doc for follower read #20703
Conversation
Signed-off-by: you06 <[email protected]>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
ti-chi-bot
bot
added
missing-translation-status
|
@you06: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
| Follower Read 功能适用于以下场景： | ||
|
|
||
| - 希望通过 follower 打散读热点。 | ||
| - 希望通过读取本地副本节省流量。 |
There was a problem hiding this comment.
这个“本地”是否展开解释成 “相同 zone tidb 访问 tikv“？
| 通过读取本地副本节省流量的使用场景推荐的设置为： | ||
|
|
||
| - 默认值 `leader` 的性能最好。 | ||
| - `closest-adaptive` 在最小性能损失的前提下尽可能节省流量。 |
There was a problem hiding this comment.
/cc @joey-yez
这个 adaptive 是否也归到不推荐使用，只保留 closest-replica 和默认 leader
|
|
||
| ### Follower 副本选择策略 | ||
|
|
||
| 由于 TiKV 的 Follower Read 不会破坏 TiDB 的 Snapshot Isolation 事务隔离级别，因此 TiDB 选择 follower 的策略可以采用 round robin 的方式。目前，对于 Coprocessor 请求，Follower Read 负载均衡策略粒度是连接级别的，对于一个 TiDB 的客户端连接在某个具体的 Region 上会固定使用同一个 follower，只有在选中的 follower 发生故障或者因调度策略发生调整的情况下才会进行切换。而对于非 Coprocessor 请求（点查等），Follower Read 负载均衡策略粒度是事务级别的，对于一个 TiDB 的事务在某个具体的 Region 上会固定使用同一个 follower，同样在 follower 发生故障或者因调度策略发生调整的情况下才会进行切换。如果同一事务内既有点查请求又有 Coprocessor 请求，两种请求都将按照上述调度策略分别进行读取，即使 Coprocessor 和点查出现在同一个 Region 上，TiDB 也会当作独立事件来处理。 | ||
| 由于 TiKV 的 Follower Read 不会破坏 TiDB 的 Snapshot Isolation 事务隔离级别，因此 TiDB 会根据 `tidb_replica_read` 选择满足要求的副本进行读取。当选中的 follower 节点出现无法访问的故障或其他错误时，会切换到 leader 提供服务。 |
There was a problem hiding this comment.
是否提一下这里的策略是第一轮请求处理，不包含后续内部 region error 处理和重试？
First-time contributors' checklist
What is changed, added or deleted? (Required)
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions (in Chinese).
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?