Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

remove arbiter from v8.1.1 #18420

Merged
merged 5 commits into from
Aug 27, 2024
Merged

remove arbiter from v8.1.1 #18420

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
61f30fe
remove arbiter from v8.1.0
Oreoxmt Aug 22, 2024
fe6e16b
Discard changes to releases/release-8.1.0.md
qiancai Aug 22, 2024
cbb8037
Update release-8.1.0.md
lilin90 Aug 22, 2024
5938fc7
Merge branch 'remove_arbiter' of https://github.com/Oreoxmt/docs-cn i…
lilin90 Aug 22, 2024
7dbd3e6
Update tidb-configuration-file.md
lilin90 Aug 22, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion binary-package.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,6 @@ TiDB 提供了 amd64 和 arm64 两种架构的离线包。对于每种架构，T
| binlogctl | 从 v6.0.0 起新增 |
| sync_diff_inspector | |
| reparo | |
| arbiter | |
| server-{version}-linux-{arch}.tar.gz | 从 v6.2.0 起新增 |
| grafana-{version}-linux-{arch}.tar.gz | 从 v6.2.0 起新增 |
| alertmanager-{version}-linux-{arch}.tar.gz | 从 v6.2.0 起新增 |
Expand Down
2 changes: 1 addition & 1 deletion tidb-configuration-file.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -504,7 +504,7 @@ TiDB 配置文件比命令行参数支持更多的选项。你可以在 [config/
+ TiDB 单个事务大小限制
+ 默认值：104857600
+ 单位：Byte
+ 单个事务中，所有 key-value 记录的总大小不能超过该限制。该配置项的最大值不超过 `1099511627776`（表示 1TB）。注意，如果使用了以 `Kafka` 为下游消费者的 `binlog`，如：`arbiter` 集群，该配置项的值不能超过 `1073741824`（表示 1GB），因为这是 `Kafka` 的处理单条消息的最大限制，超过该限制 `Kafka` 将会报错。
+ 单个事务中，所有 key-value 记录的总大小不能超过该限制。该配置项的最大值不超过 `1099511627776`（表示 1TB）。注意，如果使用了以 `Kafka` 为下游消费者的 `binlog`，该配置项的值不能超过 `1073741824`（表示 1GB），因为这是 `Kafka` 的处理单条消息的最大限制，超过该限制 `Kafka` 将会报错。
+ 在 v6.5.0 及之后的版本中，不再推荐使用该配置项，事务的内存大小会被累计计入所在会话的内存使用量中，并由 [`tidb_mem_quota_query`](/system-variables.md#tidb_mem_quota_query) 变量在单个会话内存超阈值时采取控制行为。为了向前兼容，由低版本升级至 v6.5.0 及更高版本时，该配置项的行为如下所述:
+ 若该配置项未设置，或设置为默认值 (`104857600`)，升级后事务内存大小将会计入所在会话的内存使用中，由 `tidb_mem_quota_query` 变量控制。
+ 若该配置项未设为默认值 (`104857600`)，升级前后该配置项仍生效，对单个事务大小的限制行为不会发生变化，事务内存大小不由 `tidb_mem_quota_query` 控制。
Expand Down