Skip to content
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

[8.15] Fix link to 8.15.x memory queue issue in Beats. (backport #1464) #1473

Merged
merged 1 commit into from
Nov 18, 2024
Merged

[8.15] Fix link to 8.15.x memory queue issue in Beats. (backport #1464) #1473

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 4 additions & 4 deletions docs/en/ingest-management/release-notes/release-notes-8.15.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@ Review important information about the {fleet} and {agent} 8.15.3 release.

In 8.15, events in the memory queue are not freed when they are acknowledged (as intended), but only when they are overwritten by later events in the queue buffer. This means for example if a configuration has a queue size of 5000, but the input data is low-volume and only 100 events are active at once, then the queue will gradually store more events until reaching 5000 in memory at once, then start replacing those with new events.

See {beats} issue link:https://github.com/elastic/beats/issues/40705[#40705].
See {beats} issue link:https://github.com/elastic/beats/issues/41355[#41355].

*Impact* +

Expand Down Expand Up @@ -117,7 +117,7 @@ Review important information about the {fleet} and {agent} 8.15.2 release.

In 8.15, events in the memory queue are not freed when they are acknowledged (as intended), but only when they are overwritten by later events in the queue buffer. This means for example if a configuration has a queue size of 5000, but the input data is low-volume and only 100 events are active at once, then the queue will gradually store more events until reaching 5000 in memory at once, then start replacing those with new events.

See {beats} issue link:https://github.com/elastic/beats/issues/40705[#40705].
See {beats} issue link:https://github.com/elastic/beats/issues/41355[#41355].

*Impact* +

Expand Down Expand Up @@ -226,7 +226,7 @@ same package versions.

In 8.15, events in the memory queue are not freed when they are acknowledged (as intended), but only when they are overwritten by later events in the queue buffer. This means for example if a configuration has a queue size of 5000, but the input data is low-volume and only 100 events are active at once, then the queue will gradually store more events until reaching 5000 in memory at once, then start replacing those with new events.

See {beats} issue link:https://github.com/elastic/beats/issues/40705[#40705].
See {beats} issue link:https://github.com/elastic/beats/issues/41355[#41355].

*Impact* +

Expand Down Expand Up @@ -285,7 +285,7 @@ If you're using {agent} on Windows with any integration which makes use of the A

In 8.15, events in the memory queue are not freed when they are acknowledged (as intended), but only when they are overwritten by later events in the queue buffer. This means for example if a configuration has a queue size of 5000, but the input data is low-volume and only 100 events are active at once, then the queue will gradually store more events until reaching 5000 in memory at once, then start replacing those with new events.

See {beats} issue link:https://github.com/elastic/beats/issues/40705[#40705].
See {beats} issue link:https://github.com/elastic/beats/issues/41355[#41355].

*Impact* +

Expand Down