aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authoralextarazanov <alextarazanov@yandex-team.com>2022-11-02 16:50:15 +0300
committeralextarazanov <alextarazanov@yandex-team.com>2022-11-02 16:50:15 +0300
commitc3ef50c0089b7fa72ffe9a6bc883a14b1069c622 (patch)
treeb1060d16f06d9d75fce3ab55428bb1852ee850af
parente7b6303dfaa19ae40b8b8585110056a484367c07 (diff)
downloadydb-c3ef50c0089b7fa72ffe9a6bc883a14b1069c622.tar.gz
[review] [YDB] "TTL run internal" check translate
-rw-r--r--ydb/docs/en/core/concepts/_includes/ttl.md3
1 files changed, 1 insertions, 2 deletions
diff --git a/ydb/docs/en/core/concepts/_includes/ttl.md b/ydb/docs/en/core/concepts/_includes/ttl.md
index 6901ff29ddf..96532267146 100644
--- a/ydb/docs/en/core/concepts/_includes/ttl.md
+++ b/ydb/docs/en/core/concepts/_includes/ttl.md
@@ -36,8 +36,7 @@ The *BRO* has the following properties:
## Guarantees {#guarantees}
-* At every point in time, a *BRO* is run in no more than 1 instance per table.
-* *BROs* are run no more than once per hour for the same shard.
+* For the same partition *BRO* is run at the intervals set in the TTL settings. The default run interval is 1 hour, the minimum allowable value is 15 minutes.
* Data consistency is guaranteed. The TTL column value is re-checked during the delete stage. This means that if the TTL column value is updated between stages 1 and 2 (for example, with `UPDATE`) and ceases to meet the delete criteria, the row will not be deleted.
## Limitations {#restrictions}