From 7e1d859cf79d339baea42c818659360b6398e9fd Mon Sep 17 00:00:00 2001 From: "mergify[bot]" <37929162+mergify[bot]@users.noreply.github.com> Date: Wed, 23 Oct 2024 10:46:02 +0200 Subject: [PATCH] [main](backport #41379) Document 8.15 memory usage regression as a known issue. (#41380) * Document memory usage regression as a known issue. (#41379) (cherry picked from commit f8bd07d239e18ad9e50488116565e9a2cca19137) # Conflicts: # CHANGELOG.asciidoc * Fix conflicts --------- Co-authored-by: Craig MacKenzie (cherry picked from commit 1aa9ef69d3d93330605287a2f6fb7c83e1d99a5f) # Conflicts: # CHANGELOG.asciidoc --- CHANGELOG.asciidoc | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/CHANGELOG.asciidoc b/CHANGELOG.asciidoc index a3ba0f415ad..955744b0b33 100644 --- a/CHANGELOG.asciidoc +++ b/CHANGELOG.asciidoc @@ -7,6 +7,12 @@ === Beats version 8.15.3 https://github.com/elastic/beats/compare/v8.15.2\...v8.15.3[View commits] +==== Known issues + +*Affecting all Beats* + +- Memory usage is not correctly limited by the number of events actively in the memory queue, but rather the maximum size of the memory queue regardless of usage. {issue}41355[41355] + ==== Breaking changes *Filebeat* @@ -54,6 +60,12 @@ https://github.com/elastic/beats/compare/v8.15.0\...v8.15.2[View commits] - Beats Docker images do not log to stderr by default. The workaround is to pass the CLI flag `-e` or to set `logging.to_stderr: true` in the configuration file. {issue}41118[41118] +==== Known issues + +*Affecting all Beats* + +- Memory usage is not correctly limited by the number of events actively in the memory queue, but rather the maximum size of the memory queue regardless of usage. {issue}41355[41355] + ==== Bugfixes *Affecting all Beats* @@ -73,7 +85,13 @@ https://github.com/elastic/beats/compare/v8.15.0\...v8.15.1[View commits] *Affecting all Beats* +<<<<<<< HEAD +- Beats stop publishing data after a network error unless restarted. Avoid upgrading to 8.15.1. Affected Beats log `Get \"https://${ELASTICSEARCH_HOST}:443\": context canceled` repeatedly. {issue}40705{40705} +======= +- Beats Docker images do not log to stderr by default. The workaround is to pass the CLI flag `-e` or to set `logging.to_stderr: true` in the configuration file. - Beats stop publishing data after a network error unless restarted. Avoid upgrading to 8.15.1. Affected Beats log `Get \"https://${ELASTICSEARCH_HOST}:443\": context canceled` repeatedly. {issue}40705{40705} +- Memory usage is not correctly limited by the number of events actively in the memory queue, but rather the maximum size of the memory queue regardless of usage. {issue}41355[41355] +>>>>>>> 1aa9ef69d3 ([main](backport #41379) Document 8.15 memory usage regression as a known issue. (#41380)) ==== Bugfixes @@ -126,6 +144,7 @@ https://github.com/elastic/beats/compare/v8.14.3\...v8.15.0[View commits] *Filebeat* - The Azure EventHub input in Filebeat is not found when running on Windows. Please refrain from upgrading to 8.15. See {issue}40608[40608] for details. +- Memory usage is not correctly limited by the number of events actively in the memory queue, but rather the maximum size of the memory queue regardless of usage. {issue}41355[41355] ==== Breaking changes