From fb9164446885bfa1b9875f36d85caf6e1338d6bc Mon Sep 17 00:00:00 2001 From: Lior Kogan Date: Fri, 21 Feb 2025 16:57:33 +0200 Subject: [PATCH 1/3] COMPACTION_POLICY - added warning --- content/develop/data-types/timeseries/configuration.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/content/develop/data-types/timeseries/configuration.md b/content/develop/data-types/timeseries/configuration.md index 25650781f0..fd898e16f8 100644 --- a/content/develop/data-types/timeseries/configuration.md +++ b/content/develop/data-types/timeseries/configuration.md @@ -125,6 +125,12 @@ Each rule is separated by a semicolon (`;`), the rule consists of multiple field Assure that there is a bucket that starts at exactly _alignTimestamp_ after the epoch and align all other buckets accordingly. Default value: 0 (aligned with the epoch). Example: if _bucketDuration_ is 24 hours, setting _alignTimestamp_ to `6h` (6 hours after the Epoch) will ensure that each bucket’s timeframe is [06:00 .. 06:00). +{{% warning %}} +On a clustered environment, if `COMPACTION_POLICY` is set, you must use [hash tags]({{< relref "/operate/oss_and_stack/reference/cluster-spec" >}}#hash-tags) for all time series key names. +This will force each compaction to be created in the same hash slot as its source key. +Failure to do so can result in data not being compacted with no error messages. +{{% /warning %}} + When a compaction policy is defined, compaction rules will be created automatically for newly created time series, and their key would be set to: * If the time bucket alignment is 0: From 9e2f2e3e3c0da173fcd1d4aca7d20f448b7532d0 Mon Sep 17 00:00:00 2001 From: David Dougherty Date: Fri, 21 Feb 2025 07:42:08 -0800 Subject: [PATCH 2/3] Active voice edit. --- content/develop/data-types/timeseries/configuration.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/content/develop/data-types/timeseries/configuration.md b/content/develop/data-types/timeseries/configuration.md index fd898e16f8..37661b6318 100644 --- a/content/develop/data-types/timeseries/configuration.md +++ b/content/develop/data-types/timeseries/configuration.md @@ -126,9 +126,7 @@ Each rule is separated by a semicolon (`;`), the rule consists of multiple field Assure that there is a bucket that starts at exactly _alignTimestamp_ after the epoch and align all other buckets accordingly. Default value: 0 (aligned with the epoch). Example: if _bucketDuration_ is 24 hours, setting _alignTimestamp_ to `6h` (6 hours after the Epoch) will ensure that each bucket’s timeframe is [06:00 .. 06:00). {{% warning %}} -On a clustered environment, if `COMPACTION_POLICY` is set, you must use [hash tags]({{< relref "/operate/oss_and_stack/reference/cluster-spec" >}}#hash-tags) for all time series key names. -This will force each compaction to be created in the same hash slot as its source key. -Failure to do so can result in data not being compacted with no error messages. +In a clustered environment, if you set `COMPACTION_POLICY`, you must use [hash tags]({{< relref "/operate/oss_and_stack/reference/cluster-spec" >}}#hash-tags) for all time series key names. This ensures that the system creates each compaction in the same hash slot as its source key. If you don't, the system may fail to compact the data without displaying any error messages. {{% /warning %}} When a compaction policy is defined, compaction rules will be created automatically for newly created time series, and their key would be set to: From 88294a795f678cfed5ab02daf69d520ebea6f607 Mon Sep 17 00:00:00 2001 From: David Dougherty Date: Fri, 21 Feb 2025 07:49:28 -0800 Subject: [PATCH 3/3] Apply review comments. --- content/develop/data-types/timeseries/configuration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/develop/data-types/timeseries/configuration.md b/content/develop/data-types/timeseries/configuration.md index 37661b6318..83f559503c 100644 --- a/content/develop/data-types/timeseries/configuration.md +++ b/content/develop/data-types/timeseries/configuration.md @@ -126,7 +126,7 @@ Each rule is separated by a semicolon (`;`), the rule consists of multiple field Assure that there is a bucket that starts at exactly _alignTimestamp_ after the epoch and align all other buckets accordingly. Default value: 0 (aligned with the epoch). Example: if _bucketDuration_ is 24 hours, setting _alignTimestamp_ to `6h` (6 hours after the Epoch) will ensure that each bucket’s timeframe is [06:00 .. 06:00). {{% warning %}} -In a clustered environment, if you set `COMPACTION_POLICY`, you must use [hash tags]({{< relref "/operate/oss_and_stack/reference/cluster-spec" >}}#hash-tags) for all time series key names. This ensures that the system creates each compaction in the same hash slot as its source key. If you don't, the system may fail to compact the data without displaying any error messages. +In a clustered environment, if you set `COMPACTION_POLICY`, you must use [hash tags]({{< relref "/operate/oss_and_stack/reference/cluster-spec" >}}#hash-tags) for all time series key names. This ensures that Redis will create each compaction in the same hash slot as its source key. If you don't, the system may fail to compact the data without displaying any error messages. {{% /warning %}} When a compaction policy is defined, compaction rules will be created automatically for newly created time series, and their key would be set to: