Skip to content

Commit 4c5619d

Browse files
authored
docs: Fix known issues unintended nested entries (elastic#17572)
1 parent faf3c07 commit 4c5619d

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

docs/release-notes/known-issues.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,13 +21,17 @@ Known issues are significant defects or limitations that may impact your impleme
2121
:::
2222

2323
:::{dropdown} Tail Sampling may not compact / expired TTLs as quickly as desired, causing increased storage usage.
24-
**Elastic Stack versions: 8.0.0+ < 9.0**
24+
25+
*Elastic Stack versions: 8.0.0+ < 9.0*
26+
2527
There are some issues with the Tail Sampling implementation in versions 8.0.0+ < 9.0 that may cause the buffered traces to not be compacted or expired as quickly as desired. This can lead to increased storage usage for longer than the default 30m TTL.
2628

2729
This may manifest in two ways, increased value log (vlog) file size and increased SST (LSM) file size. LSM growth and late compaction is particularly troublesome given how the underlying K/V database performs compactions on its layers. There is noticeable LSM growth for use-cases where traces are under 1KB in size, since they are written to the LSM layer directly.
2830

2931
This issue is fixed in 9.0.0, due to a re-implementation of how the underlying tail sampling databases are used. The new implementation uses a more efficient partitioning scheme, allowing more efficient expiration of traces.
3032

33+
:::
34+
3135
:::{dropdown} prefer_ilm required in component templates to create custom lifecycle policies
3236

3337
*Elastic Stack versions: 8.15.1+*

0 commit comments

Comments
 (0)