The two parameters are set to 0 by default. raftstore.raft-min-election-timeout-ticks: 1000 raftstore.raft-max-election-timeout-ticks: 1020 PD parameters • The PD metadata information records the topology are evicted before stopping the instance. The default timeout time is 5 minutes (300 seconds). The instance is directly stopped after this timeout time. • To perform the upgrade immediately without evicting stance are evicted before stopping the instance. You can set --transfer �→ -timeout to a larger value, for example, --transfer-timeout 3600 (unit: second). Offline upgrade 1. Before the offline upgrade, you

snapshot files when snapshot files cannot be garbage collected #10813 – Fix a panic issue caused by timeout when processing Coprocessor requests #10852 – Fix a memory leak caused by monitoring data of statistics of library nsl – Block the infinite wait of wait index when writing pressure is heavy (a default timeout of 5 minutes is added), which prevents TiFlash from waiting too long for data replication to provide of connection attempts 60 �→ exceeds the value, the backend server is considered unavailable. timeout connect 2s # The maximum time to wait for a �→ connection attempt to a backend server to succeed

the interval of the inspection. If the latency exceeds this value, this inspection is marked as timeout. The default value is 500ms. 32 Configuration file Configuration item Change type Description �→ duration �→ Modified Indicates the longest inactive duration allowed for a peer. A peer with timeout is marked as down, and PD tries to delete it later. The default value is changed from 5m to 10m. The two parameters are set to 0 by default. raftstore.raft-min-election-timeout-ticks: 1000 raftstore.raft-max-election-timeout-ticks: 1020 PD parameters • The PD metadata information records the topology

number of connection attempts �→ exceeds the value, the backend server is considered unavailable. timeout connect 2s # The maximum time to wait for a �→ connection attempt to a backend server to succeed if the server is located on the same LAN as �→ HAProxy. timeout client 30000s # The maximum inactivity time on the �→ client side. timeout server 30000s # The maximum inactivity time on the �→ server number of connection attempts �→ exceeds the value, the backend server is considered unavailable. timeout connect 2s # The maximum time to wait for a �→ connection attempt to a backend server to succeed

statistics before timeout. 33 Variable name Change type Description tidb_stats_load_pseudo_timeout �→ Newly added Controls when syn- chronously loading statistics reaches timeout, whether SQL fails PREDICATE COLUMNS information to the mysql. �→ column_stats_usage system table every 100 * stats-lease. When the query pat- tern of your business is stable, you can use the ANALYZE TABLE TableName PREDICATE #1798 * Fix the issue of replication stop caused by the incorrect configuration of config.Metadata.Timeout #3352 – TiDB Data Migration (DM) * Fix the issue that the CREATE VIEW statement interrupts data

difficult to diagnose promptly. To avoid these issues, TiDB v7.6.0 introduces the tidb_idle_transaction_timeout system variable, which automatically terminates long-running idle transactions. When a user session value of this sys- tem vari- able. 49 Variable name Change type Description tidb_idle_transaction_timeout �→ Newly added Controls the idle time- out for trans- actions in a user ses- sion. When a user session #47864 #47829 #47816 @YangKeao @lcwangchao • When obtaining the schema version, TiDB uses the KV timeout feature to read by default, reducing the impact of slow meta Region leader reads on schema version

parame- ter Change type Description TiDB tikv- �→ client �→ . �→ copr �→ -req �→ - �→ timeout �→ Newly added Sets the timeout of a single Copro- cessor request. 45 Configuration file Configuration parame- (x86_64) using readline �→ 5.1 2. Run the connection string obtained in Step 1. mysql --connect-timeout 15 -u '.root' -h -P 4000 -D test �→ --ssl-mode=VERIFY_IDENTITY --ssl-ca=/etc/ssl/cert to handle the connection timeout error “Error Code: 2013. Lost connection to MySQL server during query”? This error indicates that the query execution time exceeds the timeout limit. To resolve this issue

Schema 的租约时间，单位：秒 TiDB 进程启动参数 -L -P --binlog-socket --config --lease TiDB 进程启动参数 - 26 - 本文档使用 书栈(BookStack.CN) 构建 默认: “10” Schema 的 lease 主要用在 online schema changes 上面。这个值会影响到实际的 DDL 语句的执行 时间。大多数情况下，用户不需要修改这个值，除非您清晰的了解 所指定的证书的私钥 默认: “” 目前 TiDB 不支持加载由密码保护的私钥。 PEM 格式的受信任 CA 的证书文件路径 retry-limit skip-grant-table stats-lease tcp-keep-alive ssl-cert ssl-key ssl-ca TiDB 进程启动参数 - 30 - 本文档使用 书栈(BookStack.CN) 构建 默认: “” 当同时设置了该选项和 为空时会收集所有索引列的统计信息。 在发生增加，删除以及修改语句时，TiDB 会自动更新表的总行数以及修改的行数。这些信息会定期持久化下来， 更新的周期是 5 * stats-lease , stats-lease 的默认值是 3s，如果将其指定为 0，那么将不会自动更新。 当修改的行数与总行数的比值大于 auto-analyze-ratio 时，TiDB 会自动发起 Analyze

(x86_64) using readline �→ 5.1 2. Run the connection string obtained in Step 1. mysql --connect-timeout 15 -u '.root' -h -P 4000 -D test �→ --ssl-mode=VERIFY_IDENTITY --ssl-ca=/etc/ssl/cert to handle the connection timeout error “Error Code: 2013. Lost connection to MySQL server during query”? This error indicates that the query execution time exceeds the timeout limit. To resolve this issue issue, you can adjust the timeout settings by the following steps: 1. Launch MySQL Workbench and navigate to the Workbench Preferences page. 2. In the SQL Editor > MySQL Session section, configure the

节点发起选举时经过最少的 tick 个数和最多 经过的 tick 个数都调大，这两个参数默认设置均为 0。 raftstore.raft-min-election-timeout-ticks: 1000 raftstore.raft-max-election-timeout-ticks: 1020 PD 参数 • PD 元数据信息记录 TiKV 集群的拓扑信息，根据四个维度调度 Raft Group 副本。 replication 该方式会造成性能抖动，不会造成数据损失。 • 如果希望保持性能稳定，则需要保证 TiKV 上的所有 leader 驱逐完成后再停止该 TiKV 实例， 可以指定 --transfer-timeout 为一个更大的值，如 --transfer-timeout 3600，单位为 秒。 停机升级 在停机升级前，首先需要将整个集群关停。 tiup cluster stop 之后通过 upgrade --role strings 指定被替换的服务类型 --transfer-timeout int transfer leader 的超时时间 Global Flags: --native-ssh 使用系统默认的 SSH 客户端 --wait-timeout int 等待操作超时的时间 --ssh-timeout int SSH 连接的超时时间 -y, --yes 跳过所有的确认步骤 例如，有一个