diff --git a/docs/reference/release-notes/7.10.asciidoc b/docs/reference/release-notes/7.10.asciidoc index bb4780275da84..2d67e03d1e0e0 100644 --- a/docs/reference/release-notes/7.10.asciidoc +++ b/docs/reference/release-notes/7.10.asciidoc @@ -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 @@ -91,6 +105,16 @@ Also see <>. ** 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 @@ -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 diff --git a/docs/reference/release-notes/7.11.asciidoc b/docs/reference/release-notes/7.11.asciidoc index 2a7f43cf4b589..1c794a863503a 100644 --- a/docs/reference/release-notes/7.11.asciidoc +++ b/docs/reference/release-notes/7.11.asciidoc @@ -3,6 +3,20 @@ Also see <>. +[[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 @@ -59,6 +73,20 @@ Transform:: Also see <>. +[[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 @@ -162,6 +190,16 @@ Also see <>. 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 diff --git a/docs/reference/release-notes/7.12.asciidoc b/docs/reference/release-notes/7.12.asciidoc index 139797476104e..52fd5954c52e1 100644 --- a/docs/reference/release-notes/7.12.asciidoc +++ b/docs/reference/release-notes/7.12.asciidoc @@ -3,6 +3,20 @@ Also see <>. +[[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 @@ -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 diff --git a/docs/reference/release-notes/7.13.asciidoc b/docs/reference/release-notes/7.13.asciidoc index 576c76a61336c..9bfd8c083a854 100644 --- a/docs/reference/release-notes/7.13.asciidoc +++ b/docs/reference/release-notes/7.13.asciidoc @@ -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 diff --git a/docs/reference/release-notes/7.9.asciidoc b/docs/reference/release-notes/7.9.asciidoc index 6c536fd34a237..2181859441c14 100644 --- a/docs/reference/release-notes/7.9.asciidoc +++ b/docs/reference/release-notes/7.9.asciidoc @@ -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 @@ -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 @@ -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 @@ -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