From 80239994bd612b43a5b9fc897f68a820959bd17e Mon Sep 17 00:00:00 2001 From: Grace Cai Date: Fri, 16 Aug 2024 12:27:56 +0800 Subject: [PATCH] remove region size changes --- releases/release-8.3.0.md | 5 ----- 1 file changed, 5 deletions(-) diff --git a/releases/release-8.3.0.md b/releases/release-8.3.0.md index 69bf6a54e3839..48daa25cdb67f 100644 --- a/releases/release-8.3.0.md +++ b/releases/release-8.3.0.md @@ -229,12 +229,7 @@ Quick access: [Quick start](https://docs.pingcap.com/tidb/v8.3/quick-start-with- | -------- | -------- | -------- | -------- | | TiDB | [`tikv-client.batch-policy`](/tidb-configuration-file.md#batch-policy-new-in-v830) | Newly added | Controls the batching strategy for requests from TiDB to TiKV. | | PD | [`security.redact-info-log`](/pd-configuration-file.md#redact-info-log-new-in-v50) | Modified | Support setting the value of the PD configuration item `security.redact-info-log' to `marker` to mark sensitive information in the log with single-angle quotation marks `‹›` instead of shielding it directly. With the `marker` option, you can customize the redaction rules. | -| PD | [`schedule.max-merge-region-keys`](/pd-configuration-file.md#max-merge-region-keys) | Modified | Change the default value from `200,000` to `540,000` to accommodate the default value change of `schedule.max-merge-region-size`. This change helps reduce management pressure caused by an excessive number of Regions as the cluster size grows. | -| PD | [`schedule.max-merge-region-size`](/pd-configuration-file.md#max-merge-region-size) | Modified | Change the default value from `20` MiB to `54` MiB to accommodate the increase in the TiKV default Region size to `256` MiB. This change helps reduce management pressure caused by an excessive number of Regions as the cluster size grows. | | TiKV | [`security.redact-info-log`](/tikv-configuration-file.md#redact-info-log-new-in-v408) | Modified | Support setting the value of the TiKV configuration item `security.redact-info-log' to `marker` to mark sensitive information in the log with single-angle quotation marks `‹›` instead of shielding it directly. With the `marker` option, you can customize the redaction rules. | -| TiKV | [`coprocessor.region-split-size`](/tikv-configuration-file.md#region-split-size) | Modified | Change the default value from `96` MiB to `256` MiB. This change helps reduce management pressure caused by an excessive number of Regions as the cluster size grows. | -| TiKV | [`coprocessor.region-max-size`](/tikv-configuration-file.md#region-max-size) | Modified | Change the default value from `144` MiB to `384` MiB to accommodate the increase in `coprocessor.region-split-size` to `256` MiB. | -| TiKV | [`backup.sst-max-size`](/tikv-configuration-file.md#sst-max-size) | Modified | Change the default value from `144` MiB to `384` MiB to accommodate the increase in `coprocessor.region-max-size` to `384` MiB. | | TiFlash | [`security.redact-info-log`](/tiflash/tiflash-configuration.md#configure-the-tiflash-learnertoml-file) | Modified | Support setting the value of the TiFlash Learner configuration item `security.redact-info-log' to `marker` to mark sensitive information in the log with single-angle quotation marks `‹›` instead of shielding it directly. With the `marker` option, you can customize the redaction rules | | BR | [`--allow-pitr-from-incremental`](/br/br-incremental-guide.md#limitations) | Newly added | Controls whether incremental backups are compatible with subsequent log backups. The default value is `true`, which means that incremental backups are compatible with subsequent log backups. In the case of compatibility, the DDL to be played back is scrutinized before the incremental restore starts. |