From ab52a00624f1df1a23acc2334f51cfff960716cd Mon Sep 17 00:00:00 2001 From: Jack <56563911+jdockerty@users.noreply.github.com> Date: Fri, 12 Jul 2024 00:25:59 +0100 Subject: [PATCH] docs(clustered): clarify tuning garbage collector env vars (#5517) * docs: clarify clustered gc env tunables * docs: use suggested wording Co-authored-by: Scott Anderson --------- Co-authored-by: Scott Anderson --- .../clustered/write-data/best-practices/data-lifecycle.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/content/influxdb/clustered/write-data/best-practices/data-lifecycle.md b/content/influxdb/clustered/write-data/best-practices/data-lifecycle.md index 91420dbd5..55194db8f 100644 --- a/content/influxdb/clustered/write-data/best-practices/data-lifecycle.md +++ b/content/influxdb/clustered/write-data/best-practices/data-lifecycle.md @@ -45,6 +45,9 @@ Use the following environment variables to tune the garbage collector: - `INFLUXDB_IOX_GC_PARQUETFILE_CUTOFF`: how long to retain rows in the Catalog that reference Parquet files marked for deletion. The default is `30d`. +These values tune how aggressive the garbage collector can be. A shorter duration +value means that files can be removed at a faster pace. + {{% warn %}} To ensure there is a grace period before files and references are removed, the minimum garbage collector (GC) object store and Parquet file cutoff time is