Skip to content

Commit 07e042a

Browse files
authored
tidb: mark tidb_mpp_store_fail_ttl as deprecated (#21410)
1 parent e28930d commit 07e042a

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

system-variables.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4091,12 +4091,16 @@ As shown in this diagram, when [`tidb_enable_paging`](#tidb_enable_paging-new-in
40914091

40924092
### tidb_mpp_store_fail_ttl
40934093

4094+
> **Warning:**
4095+
>
4096+
> Starting from v9.0.0, this variable is deprecated and its value is fixed to `0s`. This means TiDB no longer needs to wait before sending queries to newly started TiFlash nodes, as delays are no longer necessary to prevent query failures.
4097+
40944098
- Scope: SESSION | GLOBAL
40954099
- Persists to cluster: Yes
40964100
- Applies to hint [SET_VAR](/optimizer-hints.md#set_varvar_namevar_value): No
40974101
- Type: Duration
4098-
- Default value: `60s`
4099-
- The newly started TiFlash node does not provide services. To prevent queries from failing, TiDB limits the tidb-server sending queries to the newly started TiFlash node. This variable indicates the time range in which the newly started TiFlash node is not sent requests.
4102+
- Default value: `0s`. In v8.5.3 and earlier versions, the default value is `60s`.
4103+
- The newly started TiFlash node does not provide services. To prevent queries from failing, TiDB limits the tidb-server from sending queries to the newly started TiFlash node. This variable indicates the time range in which the newly started TiFlash node is not sent requests.
41004104

41014105
### tidb_multi_statement_mode <span class="version-mark">New in v4.0.11</span>
41024106

0 commit comments

Comments
 (0)