Skip to content

Commit fb91644

Browse files
authored
COMPACTION_POLICY - added warning
1 parent ae39f2c commit fb91644

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

content/develop/data-types/timeseries/configuration.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -125,6 +125,12 @@ Each rule is separated by a semicolon (`;`), the rule consists of multiple field
125125

126126
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).
127127

128+
{{% warning %}}
129+
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.
130+
This will force each compaction to be created in the same hash slot as its source key.
131+
Failure to do so can result in data not being compacted with no error messages.
132+
{{% /warning %}}
133+
128134
When a compaction policy is defined, compaction rules will be created automatically for newly created time series, and their key would be set to:
129135

130136
* If the time bucket alignment is 0:

0 commit comments

Comments
 (0)