You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The `known-issue-8.15.0` anchor appears twice which breaks the docs
build. Also the existing message suggests incorrectly that
`bootstrap.memory_lock: true` is recommended.
Copy file name to clipboardExpand all lines: docs/reference/release-notes/8.15.0.asciidoc
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,11 @@ after it is killed up to four times in 24 hours. (issue: {es-issue}110530[#11053
16
16
* Pipeline aggregations under `time_series` and `categorize_text` aggregations are never
17
17
returned (issue: {es-issue}111679[#111679])
18
18
19
-
* Elasticsearch will not start on Windows machines when the recommended [bootstrap.memory_lock: true](https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-configuration-memory.html#bootstrap-memory_lock) setting is configured due to [native access refactoring](https://github.com/elastic/elasticsearch/pull/111866). The workaround for 8.15.0 is to downgrade to the previous version. This issue will be fixed in 8.15.1.
19
+
* Elasticsearch will not start on Windows machines if
20
+
[`bootstrap.memory_lock` is set to `true`](https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-configuration-memory.html#bootstrap-memory_lock).
21
+
Either downgrade to an earlier version, upgrade to 8.15.1, or else follow the
22
+
recommendation in the manual to entirely disable swap instead of using the
0 commit comments