Does the scope of tidb_replica_read in version v5.3.1 include global?

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: v5.3.1版本tidb_replica_read作用域是否包括global

| username: richardliu2021

To improve efficiency, please provide the following information. Clear problem descriptions can be resolved faster:
[TiDB Usage Environment] TiDB v5.3.1

[Summary] Setting the tidb-replica_read variable to enable follower read

[Background] After installing TiDB v5.3.1 using TiUP, setting the global tidb-replica_read variable to follower or leader-and-follower is ineffective

[Phenomenon] Setting the global variable tidb_replica_read from the default value leader to leader-and-follower or follower did not take effect

[Problem] According to the documentation, the tidb_replica_read variable supports the global scope starting from v5.3, but the setting is invalid. Is there an error in the documentation?

[Business Impact]

[TiDB Version] v5.3.1

[Application Software and Version]

[Attachments] Relevant logs and configuration information

  • TiUP Cluster Display information
  • TiUP Cluster Edit config information

Monitoring (https://metricstool.pingcap.com/)

  • TiDB-Overview Grafana monitoring
  • TiDB Grafana monitoring
  • TiKV Grafana monitoring
  • PD Grafana monitoring
  • Corresponding module logs (including logs one hour before and after the issue)

If the question is related to performance optimization or troubleshooting, please download the script and run it. Please select all and copy-paste the terminal output results for upload.

2
| username: h5n1 | Original post link

How did you test it?

3
| username: xiaohetao | Original post link

According to the documentation, it is included.

4
| username: forever | Original post link

It’s best to include the testing process, session switches, etc. together.

5
| username: richardliu2021 | Original post link

Unified reply: The testing method is incorrect. Thank you all for your responses.