Skip to content

docs: Fix known issues unintended nested entries #17572

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 11, 2025
Merged

docs: Fix known issues unintended nested entries #17572

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3949391
docs: Fix known issues unintended nested entries
carsonip Jul 11, 2025
2f8e38c
Newline
carsonip Jul 11, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion docs/release-notes/known-issues.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,13 +21,17 @@ Known issues are significant defects or limitations that may impact your impleme
:::

:::{dropdown} Tail Sampling may not compact / expired TTLs as quickly as desired, causing increased storage usage.
**Elastic Stack versions: 8.0.0+ < 9.0**

*Elastic Stack versions: 8.0.0+ < 9.0*

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.

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.

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.

:::

:::{dropdown} prefer_ilm required in component templates to create custom lifecycle policies

*Elastic Stack versions: 8.15.1+*
Expand Down
Loading