From 1b9a03c95e3cf8ccaa20226591debb66afa6df7c Mon Sep 17 00:00:00 2001 From: Aolin Date: Thu, 22 Aug 2024 15:19:51 +0800 Subject: [PATCH 1/3] remove arbiter from v8.1.0 --- binary-package.md | 1 - releases/release-8.1.0.md | 4 ++++ 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/binary-package.md b/binary-package.md index bd4f3f135c3ad..7a77fe4f557a8 100644 --- a/binary-package.md +++ b/binary-package.md @@ -64,7 +64,6 @@ The `TiDB-community-toolkit` package contains the following contents. | binlogctl | New in v6.0.0 | | sync_diff_inspector | | | reparo | | -| arbiter | | | server-{version}-linux-{arch}.tar.gz | New in v6.2.0 | | grafana-{version}-linux-{arch}.tar.gz | New in v6.2.0 | | alertmanager-{version}-linux-{arch}.tar.gz | New in v6.2.0 | diff --git a/releases/release-8.1.0.md b/releases/release-8.1.0.md index 230252c4b4129..0ee0af9077615 100644 --- a/releases/release-8.1.0.md +++ b/releases/release-8.1.0.md @@ -190,6 +190,10 @@ Compared with the previous LTS 7.5.0, 8.1.0 includes new features, improvements, | TiCDC | [`sink.debezium.output-old-value`](/ticdc/ticdc-changefeed-config.md#changefeed-configuration-parameters) | Newly added | Controls whether to output the value before the row data changes. The default value is `true`. When it is disabled, the `UPDATE` event does not output the "before" field. | | TiCDC | [`sink.open.output-old-value`](/ticdc/ticdc-changefeed-config.md#changefeed-configuration-parameters) | Newly added | Controls whether to output the value before the row data changes. The default value is `true`. When it is disabled, the `UPDATE` event does not output the "p" field. | +## Offline package changes + +In v8.1.0, `arbiter` is removed from the `TiDB-community-toolkit` [binary package](/binary-package.md). + ## Deprecated features * It is planned to redesign [the auto-evolution of execution plan bindings](/sql-plan-management.md#baseline-evolution) in subsequent releases, and the related variables and behavior will change. From 966b82c494c3b071281c7bc94ecf5b21908cb85e Mon Sep 17 00:00:00 2001 From: Grace Cai Date: Thu, 22 Aug 2024 17:22:13 +0800 Subject: [PATCH 2/3] Discard changes to releases/release-8.1.0.md --- releases/release-8.1.0.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/releases/release-8.1.0.md b/releases/release-8.1.0.md index 0ee0af9077615..230252c4b4129 100644 --- a/releases/release-8.1.0.md +++ b/releases/release-8.1.0.md @@ -190,10 +190,6 @@ Compared with the previous LTS 7.5.0, 8.1.0 includes new features, improvements, | TiCDC | [`sink.debezium.output-old-value`](/ticdc/ticdc-changefeed-config.md#changefeed-configuration-parameters) | Newly added | Controls whether to output the value before the row data changes. The default value is `true`. When it is disabled, the `UPDATE` event does not output the "before" field. | | TiCDC | [`sink.open.output-old-value`](/ticdc/ticdc-changefeed-config.md#changefeed-configuration-parameters) | Newly added | Controls whether to output the value before the row data changes. The default value is `true`. When it is disabled, the `UPDATE` event does not output the "p" field. | -## Offline package changes - -In v8.1.0, `arbiter` is removed from the `TiDB-community-toolkit` [binary package](/binary-package.md). - ## Deprecated features * It is planned to redesign [the auto-evolution of execution plan bindings](/sql-plan-management.md#baseline-evolution) in subsequent releases, and the related variables and behavior will change. From a29024f91d08f247bb79c9699874240cc81007f9 Mon Sep 17 00:00:00 2001 From: lilin90 Date: Thu, 22 Aug 2024 17:34:38 +0800 Subject: [PATCH 3/3] Update tidb-configuration-file.md --- tidb-configuration-file.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tidb-configuration-file.md b/tidb-configuration-file.md index f5788bae2873b..e36b016ced14c 100644 --- a/tidb-configuration-file.md +++ b/tidb-configuration-file.md @@ -519,7 +519,7 @@ Configuration items related to performance. - The size limit of a single transaction in TiDB. - Default value: `104857600` (in bytes) -- In a single transaction, the total size of key-value records cannot exceed this value. The maximum value of this parameter is `1099511627776` (1 TB). Note that if you have used the binlog to serve the downstream consumer Kafka (such as the `arbiter` cluster), the value of this parameter must be no more than `1073741824` (1 GB). This is because 1 GB is the upper limit of a single message size that Kafka can process. Otherwise, an error is returned if this limit is exceeded. +- In a single transaction, the total size of key-value records cannot exceed this value. The maximum value of this parameter is `1099511627776` (1 TB). Note that if you have used the binlog to serve the downstream consumer Kafka, the value of this parameter must be no more than `1073741824` (1 GB). This is because 1 GB is the upper limit of a single message size that Kafka can process. Otherwise, an error is returned if this limit is exceeded. - In TiDB v6.5.0 and later versions, this configuration is no longer recommended. The memory size of a transaction will be accumulated into the memory usage of the session, and the [`tidb_mem_quota_query`](/system-variables.md#tidb_mem_quota_query) variable will take effect when the session memory threshold is exceeded. To be compatible with previous versions, this configuration works as follows when you upgrade from an earlier version to TiDB v6.5.0 or later: - If this configuration is not set or is set to the default value (`104857600`), after an upgrade, the memory size of a transaction will be accumulated into the memory usage of the session, and the `tidb_mem_quota_query` variable will take effect. - If this configuration is not defaulted (`104857600`), it still takes effect and its behavior on controlling the size of a single transaction remains unchanged before and after the upgrade. This means that the memory size of the transaction is not controlled by the `tidb_mem_quota_query` variable.