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

Jump to bottom

Update memory leak known issue to indicate all Beats are affected, updated workaround #750

Merged
merged 3 commits into from
Dec 12, 2023
Merged

Update memory leak known issue to indicate all Beats are affected, updated workaround #750

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c05702a
Update memory leak issue to indicate all Beats are affected
kilfoyle Dec 11, 2023
3710acf
Update based on Luca's feedback
kilfoyle Dec 11, 2023
81f1b46
higher -> later
kilfoyle Dec 11, 2023
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
30 changes: 23 additions & 7 deletions docs/en/ingest-management/release-notes/release-notes-8.11.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ Also see:

Review important information about {fleet-server} and {agent} for the 8.11.2 release.

IMPORTANT: The memory leak <<known-issue-115-8.11.1,known issue>> that affects Windows users running {agent} is resolved in this release. If you're currently on {agent} version 8.11.0 or 8.11.1, we recommend upgrading to 8.11.2 to avoid the issue. If you're on an earlier version, avoid upgrading to version 8.11.0 or 8.11.1 and update directly to version 8.11.2.
IMPORTANT: The memory leak <<known-issue-115-8.11.1,known issue>> that affects Windows users running {agent} is resolved in this release. If you're currently on {agent} version 8.11.0 or 8.11.1, we strongly recommend upgrading to 8.11.2 or a later release to avoid the issue. If you're on an earlier version, avoid upgrading to version 8.11.0 or 8.11.1 and update directly to version 8.11.2 or later.

[discrete]
[[enhancements-8.11.2]]
Expand Down Expand Up @@ -85,16 +85,24 @@ IMPORTANT: Due to a memory leak issue, Windows users running {agent} are recomme

*Details*

A memory leak has been identified in {metricbeat} on Windows. The leak also affects the {agent} System integration which is implemented with {metricbeat}. The leak will eventually exhaust all memory on the host system, typically after several days.
A memory leak has been identified in {beats} on Windows. All {beats} running Elastic Stack version 8.11.0 or 8.11.1 are affected. The leak also affects the {agent} System integration which is implemented with {beats}. The leak will eventually exhaust all memory on the host system, typically after several days.

*Impact* +

This issue has been fixed in upcoming version 8.11.2. For a Windows environment, we recommend waiting for the official release of 8.11.2 before upgrading from 8.10.x or earlier.
This issue has been fixed in version 8.11.2. For a Windows environment, we strongly recommend upgrading directly to 8.11.2 or any later release.

If you're already running {agent} version 8.11.0 or 8.11.1 on Windows, we recommend disabling the `process` and `process_summary` metrics in your System integration and restarting {agent}. Note that disablling these datasets will prevent the collection of process-related metrics.
If you're already running {agent} version 8.11.0 or 8.11.1 on Windows and do not want to upgrade, we recommend that you:

. Disable the `process` and `process_summary` metrics in your System integration.
. Disable logs and metrics collection.
. Restart {agent}.

Note that disabling these datasets will prevent the collection of process-related metrics.

Another workaround is to downgrade {agent} to a version below 8.11.0. Note that this could result in missing or reindexed logs or metrics as the "state" will not be persisted after {agent} is uninstalled and reinstalled.

For {beats} we currently do not have a workaround apart from upgrading to 8.12.2 or a later release.

====

[[known-issue-169825-8.11.1]]
Expand Down Expand Up @@ -247,16 +255,24 @@ For more information, refer to {agent-pull}3593[#3593].

*Details*

A memory leak has been identified in {metricbeat} on Windows. The leak also affects the {agent} system integration which is implemented with {metricbeat}. The leak will eventually exhaust all memory on the host system, typically after several days.
A memory leak has been identified in {beats} on Windows. All {beats} running Elastic Stack version 8.11.0 or 8.11.1 are affected. The leak also affects the {agent} System integration which is implemented with {beats}. The leak will eventually exhaust all memory on the host system, typically after several days.

*Impact* +

This issue has been fixed in upcoming version 8.11.2. For a Windows environment, we recommend waiting for the official release of 8.11.2 before upgrading from 8.10.x or earlier.
This issue has been fixed in version 8.11.2. For a Windows environment, we strongly recommend upgrading directly to 8.11.2 or any higher release.

If you're already running {agent} version 8.11.0 or 8.11.1 on Windows, we recommend disabling the `process` and `process_summary` metrics in your System integration and restarting {agent}. Note that disablling these datasets will prevent the collection of process-related metrics.
If you're already running {agent} version 8.11.0 or 8.11.1 on Windows and do not want to upgrade, we recommend that you:

. Disable the `process` and `process_summary` metrics in your System integration.
. Disable logs and metrics collection.
. Restart {agent}.

Note that disabling these datasets will prevent the collection of process-related metrics.

Another workaround is to downgrade {agent} to a version below 8.11.0. Note that this could result in missing or reindexed logs or metrics as the "state" will not be persisted after {agent} is uninstalled and reinstalled.

For {beats} we currently do not have a workaround apart from upgrading to 8.12.2 or a later release.

====

[[known-issue-169825-8.11.0]]
Expand Down