From 7c8b6683b1dac60655fafb7f48ca5be360ddb98a Mon Sep 17 00:00:00 2001 From: Grace Cai Date: Fri, 3 Jul 2026 14:15:51 +0800 Subject: [PATCH 1/4] Create empty translation PR From 0d9efcaf61b5332bfe29f7e87a1ffd32b82d5d55 Mon Sep 17 00:00:00 2001 From: qiancai Date: Fri, 3 Jul 2026 14:19:59 +0800 Subject: [PATCH 2/4] storage.max-ts: reuse translation from v9.0.0 --- tikv-configuration-file.md | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/tikv-configuration-file.md b/tikv-configuration-file.md index 0b32caf8af150..3569bf0bc3a36 100644 --- a/tikv-configuration-file.md +++ b/tikv-configuration-file.md @@ -636,6 +636,33 @@ Configuration items related to the I/O rate limiter. + Value options: `"read-only"`, `"write-only"`, and `"all-io"` + Default value: `"write-only"` +## storage.max-ts + +Configuration items related to `max-ts`. + +`max-ts` is the maximum read timestamp known to the current TiKV node. It ensures linearizability and transaction concurrency control semantics for async commit and one-phase commit (1PC) transactions. + +### `action-on-invalid-update` New in v8.5.7 + ++ Determines how TiKV handles invalid `max-ts` update requests. If a read or write request uses a timestamp that exceeds **the sum of the PD TSO cached in TiKV and [`max-drift`](#max-drift-new-in-v857)**, TiKV considers it an invalid `max-ts` update request. Invalid `max-ts` update requests might break the linearizability and transaction concurrency control semantics of the TiDB cluster. ++ Value options: + + `"panic"`: TiKV panics. If the PD TSO cached in TiKV is not updated in time, TiKV uses an approximate method for validation, in which case invalid requests do not cause TiKV panic. + + `"error"`: TiKV returns an error and stops processing the request. + + `"log"`: TiKV prints an error log but still processes the request. ++ Default value: `"panic"` + +### `cache-sync-interval` New in v8.5.7 + ++ Controls the interval at which TiKV updates its local PD TSO cache. TiKV periodically retrieves the latest timestamp from PD and caches it locally to check the validity of `max-ts`. ++ Default value: `"15s"` + +### `max-drift` New in v8.5.7 + ++ Specifies the maximum time by which the timestamp of a read or write request can exceed the PD TSO cached in TiKV. ++ If a read or write request uses a timestamp that exceeds **the sum of the PD TSO cached in TiKV and `max-drift`**, TiKV considers it an invalid `max-ts` update request and handles it according to the [`action-on-invalid-update`](#action-on-invalid-update-new-in-v857) configuration. ++ Default value: `"60s"` ++ It is recommended to set this value to at least three times the value of [`cache-sync-interval`](#cache-sync-interval-new-in-v857). + ## pd ### `enable-forwarding` New in v5.0.0 From 493db1ac69b7d0ece1cca732623f728cbf07fca1 Mon Sep 17 00:00:00 2001 From: Grace Cai Date: Fri, 3 Jul 2026 14:23:50 +0800 Subject: [PATCH 3/4] Apply suggestions from code review --- tikv-configuration-file.md | 1 + 1 file changed, 1 insertion(+) diff --git a/tikv-configuration-file.md b/tikv-configuration-file.md index 3569bf0bc3a36..f234953b3e614 100644 --- a/tikv-configuration-file.md +++ b/tikv-configuration-file.md @@ -661,6 +661,7 @@ Configuration items related to `max-ts`. + Specifies the maximum time by which the timestamp of a read or write request can exceed the PD TSO cached in TiKV. + If a read or write request uses a timestamp that exceeds **the sum of the PD TSO cached in TiKV and `max-drift`**, TiKV considers it an invalid `max-ts` update request and handles it according to the [`action-on-invalid-update`](#action-on-invalid-update-new-in-v857) configuration. + Default value: `"60s"` ++ This value must be greater than [`cache-sync-interval`](#cache-sync-interval-introduced-in-v857). Otherwise, TiKV fails configuration validation and cannot start. + It is recommended to set this value to at least three times the value of [`cache-sync-interval`](#cache-sync-interval-new-in-v857). ## pd From eb1860697cd12ac276a8e777e9a6e6d60451d934 Mon Sep 17 00:00:00 2001 From: Grace Cai Date: Fri, 3 Jul 2026 14:45:24 +0800 Subject: [PATCH 4/4] Apply suggestions from code review --- tikv-configuration-file.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tikv-configuration-file.md b/tikv-configuration-file.md index f234953b3e614..18a587b047eda 100644 --- a/tikv-configuration-file.md +++ b/tikv-configuration-file.md @@ -649,7 +649,7 @@ Configuration items related to `max-ts`. + `"panic"`: TiKV panics. If the PD TSO cached in TiKV is not updated in time, TiKV uses an approximate method for validation, in which case invalid requests do not cause TiKV panic. + `"error"`: TiKV returns an error and stops processing the request. + `"log"`: TiKV prints an error log but still processes the request. -+ Default value: `"panic"` ++ Default value: `"error"` ### `cache-sync-interval` New in v8.5.7 @@ -661,7 +661,7 @@ Configuration items related to `max-ts`. + Specifies the maximum time by which the timestamp of a read or write request can exceed the PD TSO cached in TiKV. + If a read or write request uses a timestamp that exceeds **the sum of the PD TSO cached in TiKV and `max-drift`**, TiKV considers it an invalid `max-ts` update request and handles it according to the [`action-on-invalid-update`](#action-on-invalid-update-new-in-v857) configuration. + Default value: `"60s"` -+ This value must be greater than [`cache-sync-interval`](#cache-sync-interval-introduced-in-v857). Otherwise, TiKV fails configuration validation and cannot start. ++ This value must be greater than [`cache-sync-interval`](#cache-sync-interval-new-in-v857). Otherwise, TiKV fails configuration validation and cannot start. + It is recommended to set this value to at least three times the value of [`cache-sync-interval`](#cache-sync-interval-new-in-v857). ## pd