Skip to content

Commit

Permalink
reference/configuration: remove retry-limit from the config file (pin…
Browse files Browse the repository at this point in the history
  • Loading branch information
lilin90 authored Aug 26, 2019
1 parent 2b7d600 commit bd442ce
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 12 deletions.
10 changes: 4 additions & 6 deletions dev/reference/configuration/tidb-server/configuration-file.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,8 @@ summary: Learn the TiDB configuration file options that are not involved in comm
category: deployment
---

<!-- markdownlint-disable MD001 -->

# TiDB Configuration File Description

The TiDB configuration file supports more options than command line options. You can find the default configuration file in [config/config.toml.example](https://github.com/pingcap/tidb/blob/master/config/config.toml.example) and rename it to `config.toml`.
Expand Down Expand Up @@ -159,12 +161,6 @@ Configuration about performance.
- To enable `keepalive` in the TCP layer
- Default: false

### `retry-limit`

- The number of retries that TiDB makes when it encounters a `key` conflict or other errors while committing a transaction
- Default: 10
- If the number of retries exceeds `retry-limit` but the transaction still fails, TiDB returns an error

### `cross-join`

- Default: true
Expand All @@ -180,7 +176,9 @@ Configuration about performance.
- At intervals of `stats-lease`, TiDB checks for column statistics that need to be loaded to the memory
- At intervals of `200 \* stats-lease`, TiDB writes the feedback cached in the memory to the system table
- At intervals of `5 \* stats-lease`, TiDB reads the feedback in the system table, and updates the statistics cached in the memory

+ When `stats-lease` is set to 0, TiDB periodically reads the feedback in the system table, and updates the statistics cached in the memory every three seconds. But TiDB no longer automatically modifies the following statistics-related system tables:

- `mysql.stats_meta`: TiDB no longer automatically records the number of table rows that are modified by the transaction and updates it to this system table
- `mysql.stats_histograms`/`mysql.stats_buckets` and `mysql.stats_top_n`: TiDB no longer automatically analyzes and proactively updates statistics
- `mysql.stats_feedback`: TiDB no longer updates the statistics of the tables and indexes according to a part of statistics returned by the queried data
Expand Down
10 changes: 4 additions & 6 deletions v3.0/reference/configuration/tidb-server/configuration-file.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,8 @@ category: deployment
aliases: ['/docs/op-guide/tidb-config-file/']
---

<!-- markdownlint-disable MD001 -->

# TiDB Configuration File Description

The TiDB configuration file supports more options than command line options. You can find the default configuration file in [config/config.toml.example](https://github.com/pingcap/tidb/blob/master/config/config.toml.example) and rename it to `config.toml`.
Expand Down Expand Up @@ -160,12 +162,6 @@ Configuration about performance.
- To enable `keepalive` in the TCP layer
- Default: false

### `retry-limit`

- The number of retries that TiDB makes when it encounters a `key` conflict or other errors while committing a transaction
- Default: 10
- If the number of retries exceeds `retry-limit` but the transaction still fails, TiDB returns an error

### `cross-join`

- Default: true
Expand All @@ -181,7 +177,9 @@ Configuration about performance.
- At intervals of `stats-lease`, TiDB checks for column statistics that need to be loaded to the memory
- At intervals of `200 * stats-lease`, TiDB writes the feedback cached in the memory to the system table
- At intervals of `5 * stats-lease`, TiDB reads the feedback in the system table, and updates the statistics cached in the memory

+ When `stats-lease` is set to 0, TiDB periodically reads the feedback in the system table, and updates the statistics cached in the memory every three seconds. But TiDB no longer automatically modifies the following statistics-related system tables:

- `mysql.stats_meta`: TiDB no longer automatically records the number of table rows that are modified by the transaction or updates it to this system table
- `mysql.stats_histograms`/`mysql.stats_buckets` and `mysql.stats_top_n`: TiDB no longer automatically analyzes or proactively updates statistics
- `mysql.stats_feedback`: TiDB no longer updates the statistics of the tables and indexes according to a part of statistics returned by the queried data
Expand Down

0 comments on commit bd442ce

Please sign in to comment.