Skip to content

Commit 56aba17

Browse files
authored
Add aggregations/CCS memory leak as a 7.14.x known issue
There is currently no plans to back port #78404 to 7.14.x. Adding this as a known issue to the release notes for 7.14.x per discussion with @qhoxie . Please also back port this doc change to 7.14.0 and 7.14.1. Thx!
1 parent c7fb2e4 commit 56aba17

File tree

1 file changed

+16
-0
lines changed

1 file changed

+16
-0
lines changed

docs/reference/release-notes/7.14.asciidoc

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,22 @@
33

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

6+
[[known-issues-7.14.2]]
7+
[discrete]
8+
=== Known issues
9+
10+
* Aggregations: When a cross cluster search request is proxied, the memory for the aggregations on the
11+
proxy node will not be freed. The trigger is cross cluster search using aggregations where minimize
12+
roundtrips is not effective (e.g. when minimize roundtrips is explicitly disabled, or implicitly disabled
13+
when using scroll, async and point in time searches). This issue can happen in all modes of remote connections
14+
configured for cross cluster search (sniff and proxy). In sniff mode, we only connect to a subset of the
15+
remote nodes (by default 3). So if the remote node we want to send a request to is not one of those 3,
16+
we must send the request as a proxy request. The workaround is to periodically restart nodes with heap pressure
17+
or cancel the aggregation tasks on the nodes.
18+
+
19+
We have fixed this issue in {es} 7.15.1 and later versions. For more details,
20+
see {es-pull}78404[#78404].
21+
622
[[enhancement-7.14.2]]
723
[float]
824
=== Enhancements

0 commit comments

Comments
 (0)