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

Document #73456 as a known issue #73471

Merged
merged 2 commits into from
May 27, 2021
Merged

Document #73456 as a known issue #73471

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f42fe7a
Document #73456 as a known issue
DaveCTurner May 27, 2021
708fbf3
Add docs to all patch releases
DaveCTurner May 27, 2021
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
34 changes: 34 additions & 0 deletions docs/reference/release-notes/7.10.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,20 @@ All versions of {es} between 7.7.0 and 7.10.1 are affected by this flaw.
You must upgrade to {es} version 7.10.2 to obtain the fix.
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22132[CVE-2021-22132]

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

* Snapshot and restore: If an index is deleted while the cluster is
concurrently taking more than one snapshot then there is a risk that one of the
snapshots may never complete and also that some shard data may be lost from the
repository, causing future restore operations to fail. To mitigate this
problem, prevent concurrent snapshot operations by setting
`snapshot.max_concurrent_operations: 1`.
+
This issue is fixed in {es} versions 7.13.1 and later. For more details, see
{es-issue}73456[#73456].

[[bug-7.10.2]]
[float]
=== Bug fixes
Expand Down Expand Up @@ -91,6 +105,16 @@ Also see <<breaking-changes-7.10,Breaking changes in 7.10>>.
** With nested `inner_hits`, the fast vector highlighter may load snippets from the wrong document. ({es-issue}65533[#65533])
** When _source is disabled, we can fail load nested `inner_hits` and `top_hits`. ({es-issue}66572[#66572])

* Snapshot and restore: If an index is deleted while the cluster is
concurrently taking more than one snapshot then there is a risk that one of the
snapshots may never complete and also that some shard data may be lost from the
repository, causing future restore operations to fail. To mitigate this
problem, prevent concurrent snapshot operations by setting
`snapshot.max_concurrent_operations: 1`.
+
This issue is fixed in {es} versions 7.13.1 and later. For more details, see
{es-issue}73456[#73456].

[[bug-7.10.1]]
[float]
=== Bug fixes
Expand Down Expand Up @@ -187,6 +211,16 @@ see {es-issue}65488[#65488].
** With nested `inner_hits`, the fast vector highlighter may load snippets from the wrong document. ({es-issue}65533[#65533])
** When _source is disabled, we can fail load nested `inner_hits` and `top_hits`. ({es-issue}66572[#66572])

* Snapshot and restore: If an index is deleted while the cluster is
concurrently taking more than one snapshot then there is a risk that one of the
snapshots may never complete and also that some shard data may be lost from the
repository, causing future restore operations to fail. To mitigate this
problem, prevent concurrent snapshot operations by setting
`snapshot.max_concurrent_operations: 1`.
+
This issue is fixed in {es} versions 7.13.1 and later. For more details, see
{es-issue}73456[#73456].

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

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

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

* Snapshot and restore: If an index is deleted while the cluster is
concurrently taking more than one snapshot then there is a risk that one of the
snapshots may never complete and also that some shard data may be lost from the
repository, causing future restore operations to fail. To mitigate this
problem, prevent concurrent snapshot operations by setting
`snapshot.max_concurrent_operations: 1`.
+
This issue is fixed in {es} versions 7.13.1 and later. For more details, see
{es-issue}73456[#73456].

[[enhancement-7.11.2]]
[float]
=== Enhancements
Expand Down Expand Up @@ -59,6 +73,20 @@ Transform::

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

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

* Snapshot and restore: If an index is deleted while the cluster is
concurrently taking more than one snapshot then there is a risk that one of the
snapshots may never complete and also that some shard data may be lost from the
repository, causing future restore operations to fail. To mitigate this
problem, prevent concurrent snapshot operations by setting
`snapshot.max_concurrent_operations: 1`.
+
This issue is fixed in {es} versions 7.13.1 and later. For more details, see
{es-issue}73456[#73456].

[[enhancement-7.11.1]]
[float]
=== Enhancements
Expand Down Expand Up @@ -162,6 +190,16 @@ Also see <<breaking-changes-7.11,Breaking changes in 7.11>>.
sizes may increase much higher than required. Elasticsearch 7.13.0 contains a fix for this.
For more details, see {es-issue}72509[#72509]

* Snapshot and restore: If an index is deleted while the cluster is
concurrently taking more than one snapshot then there is a risk that one of the
snapshots may never complete and also that some shard data may be lost from the
repository, causing future restore operations to fail. To mitigate this
problem, prevent concurrent snapshot operations by setting
`snapshot.max_concurrent_operations: 1`.
+
This issue is fixed in {es} versions 7.13.1 and later. For more details, see
{es-issue}73456[#73456].

[discrete]
[[fips-140-2-compliance-7.11.0]]
=== FIPS 140-2 compliance
Expand Down
24 changes: 24 additions & 0 deletions docs/reference/release-notes/7.12.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,20 @@

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

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

* Snapshot and restore: If an index is deleted while the cluster is
concurrently taking more than one snapshot then there is a risk that one of the
snapshots may never complete and also that some shard data may be lost from the
repository, causing future restore operations to fail. To mitigate this
problem, prevent concurrent snapshot operations by setting
`snapshot.max_concurrent_operations: 1`.
+
This issue is fixed in {es} versions 7.13.1 and later. For more details, see
{es-issue}73456[#73456].

[[enhancement-7.12.1]]
[float]
=== Enhancements
Expand Down Expand Up @@ -134,6 +148,16 @@ https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22137[CVE-2021-22137]
sizes may increase much higher than required. Elasticsearch 7.13.0 contains a fix for this.
For more details, see {es-issue}72509[#72509]

* Snapshot and restore: If an index is deleted while the cluster is
concurrently taking more than one snapshot then there is a risk that one of the
snapshots may never complete and also that some shard data may be lost from the
repository, causing future restore operations to fail. To mitigate this
problem, prevent concurrent snapshot operations by setting
`snapshot.max_concurrent_operations: 1`.
+
This issue is fixed in {es} versions 7.13.1 and later. For more details, see
{es-issue}73456[#73456].

[[breaking-7.12.0]]
[float]
=== Breaking changes
Expand Down
10 changes: 10 additions & 0 deletions docs/reference/release-notes/7.13.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,16 @@ maximum value of `512`. This allows autoscaling to run reliably as it relies on
assigning jobs only via memory. Having `xpack.ml.max_open_jobs` as a small
number may cause autoscaling to behave unexpectedly.

* Snapshot and restore: If an index is deleted while the cluster is
concurrently taking more than one snapshot then there is a risk that one of the
snapshots may never complete and also that some shard data may be lost from the
repository, causing future restore operations to fail. To mitigate this
problem, prevent concurrent snapshot operations by setting
`snapshot.max_concurrent_operations: 1`.
+
This issue is fixed in {es} versions 7.13.1 and later. For more details, see
{es-issue}73456[#73456].

[[deprecation-7.13.0]]
[float]
=== Deprecations
Expand Down
40 changes: 40 additions & 0 deletions docs/reference/release-notes/7.9.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,16 @@ with a `NOT IN` operator.
We have fixed this issue in {es} 7.10.1 and later versions. For more details,
see {es-issue}65488[#65488].

* Snapshot and restore: If an index is deleted while the cluster is
concurrently taking more than one snapshot then there is a risk that one of the
snapshots may never complete and also that some shard data may be lost from the
repository, causing future restore operations to fail. To mitigate this
problem, prevent concurrent snapshot operations by setting
`snapshot.max_concurrent_operations: 1`.
+
This issue is fixed in {es} versions 7.13.1 and later. For more details, see
{es-issue}73456[#73456].

[[bug-7.9.3]]
[float]
=== Bug fixes
Expand Down Expand Up @@ -94,6 +104,16 @@ with a `NOT IN` operator.
We have fixed this issue in {es} 7.10.1 and later versions. For more details,
see {es-issue}65488[#65488].

* Snapshot and restore: If an index is deleted while the cluster is
concurrently taking more than one snapshot then there is a risk that one of the
snapshots may never complete and also that some shard data may be lost from the
repository, causing future restore operations to fail. To mitigate this
problem, prevent concurrent snapshot operations by setting
`snapshot.max_concurrent_operations: 1`.
+
This issue is fixed in {es} versions 7.13.1 and later. For more details, see
{es-issue}73456[#73456].

[[deprecation-7.9.2]]
[float]
=== Deprecations
Expand Down Expand Up @@ -203,6 +223,16 @@ with a `NOT IN` operator.
We have fixed this issue in {es} 7.10.1 and later versions. For more details,
see {es-issue}65488[#65488].

* Snapshot and restore: If an index is deleted while the cluster is
concurrently taking more than one snapshot then there is a risk that one of the
snapshots may never complete and also that some shard data may be lost from the
repository, causing future restore operations to fail. To mitigate this
problem, prevent concurrent snapshot operations by setting
`snapshot.max_concurrent_operations: 1`.
+
This issue is fixed in {es} versions 7.13.1 and later. For more details, see
{es-issue}73456[#73456].

[[feature-7.9.1]]
[float]
=== New features
Expand Down Expand Up @@ -360,6 +390,16 @@ with a `NOT IN` operator.
We have fixed this issue in {es} 7.10.1 and later versions. For more details,
see {es-issue}65488[#65488].

* Snapshot and restore: If an index is deleted while the cluster is
concurrently taking more than one snapshot then there is a risk that one of the
snapshots may never complete and also that some shard data may be lost from the
repository, causing future restore operations to fail. To mitigate this
problem, prevent concurrent snapshot operations by setting
`snapshot.max_concurrent_operations: 1`.
+
This issue is fixed in {es} versions 7.13.1 and later. For more details, see
{es-issue}73456[#73456].

[[breaking-7.9.0]]
[discrete]
=== Breaking changes
Expand Down