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

[7.x] [DOCS] Add aggregations/CCS memory leak as a 7.14.x known issue (#78728) #78789

Merged
merged 1 commit into from
Oct 6, 2021
Merged

[7.x] [DOCS] Add aggregations/CCS memory leak as a 7.14.x known issue (#78728) #78789

Show file tree
Hide file tree
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
32 changes: 32 additions & 0 deletions docs/reference/release-notes/7.14.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,26 @@

Also see <<breaking-changes-7.14,Breaking changes in 7.14>>.

[[known-issues-7.14.2]]
[discrete]
=== Known issues

// tag::ccs-agg-mem-known-issue[]
* Aggregations: In {es} 7.14.0–7.15.0, when a {ccs} ({ccs-init}) request is proxied, the memory for the aggregations on the
proxy node will not be freed. The trigger is {ccs} using aggregations where minimize
roundtrips is not effective (for example, when minimize roundtrips is explicitly disabled, or implicitly disabled
when using scroll, async and point-in-time searches).
+
This affects {kib} {ccs-init} aggregations because {kib}
uses async search by default. This issue can also happen in all modes of remote connections
configured for {ccs} (sniff and proxy). In sniff mode, we only connect to a subset of the
remote nodes (by default 3). So if the remote node we want to send a request to is not one of those 3,
we must send the request as a proxy request. The workaround is to periodically restart nodes with heap pressure.
+
We have fixed this issue in {es} 7.15.1 and later versions. For more details,
see {es-pull}78404[#78404].
// end::ccs-agg-mem-known-issue[]

[[enhancement-7.14.2]]
[float]
=== Enhancements
Expand Down Expand Up @@ -34,6 +54,12 @@ Snapshot/Restore::

Also see <<breaking-changes-7.14,Breaking changes in 7.14>>.

[[known-issues-7.14.1]]
[discrete]
=== Known issues

include::7.14.asciidoc[tag=ccs-agg-mem-known-issue]

[[enhancement-7.14.1]]
[float]
=== Enhancements
Expand Down Expand Up @@ -129,6 +155,12 @@ Packaging::

Also see <<breaking-changes-7.14,Breaking changes in 7.14>>.

[[known-issues-7.14.0]]
[discrete]
=== Known issues

include::7.14.asciidoc[tag=ccs-agg-mem-known-issue]

[[breaking-7.14.0]]
[float]
=== Breaking changes
Expand Down
6 changes: 6 additions & 0 deletions docs/reference/release-notes/7.15.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,12 @@

Also see <<breaking-changes-7.15,Breaking changes in 7.15>>.

[[known-issues-7.15.0]]
[discrete]
=== Known issues

include::7.14.asciidoc[tag=ccs-agg-mem-known-issue]

[[breaking-7.15.0]]
[float]
=== Breaking changes
Expand Down