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

Jump to bottom

[8.15] Update known-issues for the features upgrade bug #111030

Merged
merged 1 commit into from
Jul 18, 2024
Merged

[8.15] Update known-issues for the features upgrade bug #111030

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
7 changes: 7 additions & 0 deletions docs/reference/release-notes/8.12.0.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,13 @@ there are deleted documents in the segments, quantiles may fail to build and pre

This issue is fixed in 8.12.1.

* When upgrading clusters from version 8.11.4 or earlier, if your cluster contains non-master-eligible nodes,
information about the new functionality of these upgraded nodes may not be registered properly with the master node.
This can lead to some new functionality added since 8.12.0 not being accessible on the upgraded cluster.
If your cluster is running on ECK 2.12.1 and above, this may cause problems with finalizing the upgrade.
To resolve this issue, perform a rolling restart on the non-master-eligible nodes once all Elasticsearch nodes
are upgraded. This issue is fixed in 8.15.0.

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

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

[[known-issues-8.12.1]]
[float]
=== Known issues
* When upgrading clusters from version 8.11.4 or earlier, if your cluster contains non-master-eligible nodes,
information about the new functionality of these upgraded nodes may not be registered properly with the master node.
This can lead to some new functionality added since 8.12.0 not being accessible on the upgraded cluster.
If your cluster is running on ECK 2.12.1 and above, this may cause problems with finalizing the upgrade.
To resolve this issue, perform a rolling restart on the non-master-eligible nodes once all Elasticsearch nodes
are upgraded. This issue is fixed in 8.15.0.

[[bug-8.12.1]]
[float]
=== Bug fixes
Expand Down
10 changes: 10 additions & 0 deletions docs/reference/release-notes/8.12.2.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,16 @@

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

[[known-issues-8.12.2]]
[float]
=== Known issues
* When upgrading clusters from version 8.11.4 or earlier, if your cluster contains non-master-eligible nodes,
information about the new functionality of these upgraded nodes may not be registered properly with the master node.
This can lead to some new functionality added since 8.12.0 not being accessible on the upgraded cluster.
If your cluster is running on ECK 2.12.1 and above, this may cause problems with finalizing the upgrade.
To resolve this issue, perform a rolling restart on the non-master-eligible nodes once all Elasticsearch nodes
are upgraded. This issue is fixed in 8.15.0.

[[bug-8.12.2]]
[float]
=== Bug fixes
Expand Down
6 changes: 3 additions & 3 deletions docs/reference/release-notes/8.13.0.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,12 +21,12 @@ This affects clusters running version 8.10 or later, with an active downsampling
https://www.elastic.co/guide/en/elasticsearch/reference/current/downsampling-ilm.html[configuration]
or a configuration that was activated at some point since upgrading to version 8.10 or later.

* When upgrading clusters from version 8.12.2 or earlier, if your cluster contains non-master-eligible nodes,
* When upgrading clusters from version 8.11.4 or earlier, if your cluster contains non-master-eligible nodes,
information about the new functionality of these upgraded nodes may not be registered properly with the master node.
This can lead to some new functionality added since 8.13.0 not being accessible on the upgraded cluster.
This can lead to some new functionality added since 8.12.0 not being accessible on the upgraded cluster.
If your cluster is running on ECK 2.12.1 and above, this may cause problems with finalizing the upgrade.
To resolve this issue, perform a rolling restart on the non-master-eligible nodes once all Elasticsearch nodes
are upgraded.
are upgraded. This issue is fixed in 8.15.0.

[[breaking-8.13.0]]
[float]
Expand Down
6 changes: 3 additions & 3 deletions docs/reference/release-notes/8.13.1.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,12 +6,12 @@ Also see <<breaking-changes-8.13,Breaking changes in 8.13>>.
[[known-issues-8.13.1]]
[float]
=== Known issues
* When upgrading clusters from version 8.12.2 or earlier, if your cluster contains non-master-eligible nodes,
* When upgrading clusters from version 8.11.4 or earlier, if your cluster contains non-master-eligible nodes,
information about the new functionality of these upgraded nodes may not be registered properly with the master node.
This can lead to some new functionality added since 8.13.0 not being accessible on the upgraded cluster.
This can lead to some new functionality added since 8.12.0 not being accessible on the upgraded cluster.
If your cluster is running on ECK 2.12.1 and above, this may cause problems with finalizing the upgrade.
To resolve this issue, perform a rolling restart on the non-master-eligible nodes once all Elasticsearch nodes
are upgraded.
are upgraded. This issue is fixed in 8.15.0.

[[bug-8.13.1]]
[float]
Expand Down
6 changes: 3 additions & 3 deletions docs/reference/release-notes/8.13.2.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,12 +6,12 @@ Also see <<breaking-changes-8.13,Breaking changes in 8.13>>.
[[known-issues-8.13.2]]
[float]
=== Known issues
* When upgrading clusters from version 8.12.2 or earlier, if your cluster contains non-master-eligible nodes,
* When upgrading clusters from version 8.11.4 or earlier, if your cluster contains non-master-eligible nodes,
information about the new functionality of these upgraded nodes may not be registered properly with the master node.
This can lead to some new functionality added since 8.13.0 not being accessible on the upgraded cluster.
This can lead to some new functionality added since 8.12.0 not being accessible on the upgraded cluster.
If your cluster is running on ECK 2.12.1 and above, this may cause problems with finalizing the upgrade.
To resolve this issue, perform a rolling restart on the non-master-eligible nodes once all Elasticsearch nodes
are upgraded.
are upgraded. This issue is fixed in 8.15.0.

[[bug-8.13.2]]
[float]
Expand Down
6 changes: 3 additions & 3 deletions docs/reference/release-notes/8.13.3.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,12 +13,12 @@ SQL::
[[known-issues-8.13.3]]
[float]
=== Known issues
* When upgrading clusters from version 8.12.2 or earlier, if your cluster contains non-master-eligible nodes,
* When upgrading clusters from version 8.11.4 or earlier, if your cluster contains non-master-eligible nodes,
information about the new functionality of these upgraded nodes may not be registered properly with the master node.
This can lead to some new functionality added since 8.13.0 not being accessible on the upgraded cluster.
This can lead to some new functionality added since 8.12.0 not being accessible on the upgraded cluster.
If your cluster is running on ECK 2.12.1 and above, this may cause problems with finalizing the upgrade.
To resolve this issue, perform a rolling restart on the non-master-eligible nodes once all Elasticsearch nodes
are upgraded.
are upgraded. This issue is fixed in 8.15.0.

[[bug-8.13.3]]
[float]
Expand Down
6 changes: 3 additions & 3 deletions docs/reference/release-notes/8.13.4.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,12 +6,12 @@ Also see <<breaking-changes-8.13,Breaking changes in 8.13>>.
[[known-issues-8.13.4]]
[float]
=== Known issues
* When upgrading clusters from version 8.12.2 or earlier, if your cluster contains non-master-eligible nodes,
* When upgrading clusters from version 8.11.4 or earlier, if your cluster contains non-master-eligible nodes,
information about the new functionality of these upgraded nodes may not be registered properly with the master node.
This can lead to some new functionality added since 8.13.0 not being accessible on the upgraded cluster.
This can lead to some new functionality added since 8.12.0 not being accessible on the upgraded cluster.
If your cluster is running on ECK 2.12.1 and above, this may cause problems with finalizing the upgrade.
To resolve this issue, perform a rolling restart on the non-master-eligible nodes once all Elasticsearch nodes
are upgraded.
are upgraded. This issue is fixed in 8.15.0.

[[bug-8.13.4]]
[float]
Expand Down
6 changes: 3 additions & 3 deletions docs/reference/release-notes/8.14.0.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,12 +15,12 @@ Security::
[[known-issues-8.14.0]]
[float]
=== Known issues
* When upgrading clusters from version 8.12.2 or earlier, if your cluster contains non-master-eligible nodes,
* When upgrading clusters from version 8.11.4 or earlier, if your cluster contains non-master-eligible nodes,
information about the new functionality of these upgraded nodes may not be registered properly with the master node.
This can lead to some new functionality added since 8.13.0 not being accessible on the upgraded cluster.
This can lead to some new functionality added since 8.12.0 not being accessible on the upgraded cluster.
If your cluster is running on ECK 2.12.1 and above, this may cause problems with finalizing the upgrade.
To resolve this issue, perform a rolling restart on the non-master-eligible nodes once all Elasticsearch nodes
are upgraded.
are upgraded. This issue is fixed in 8.15.0.

[[bug-8.14.0]]
[float]
Expand Down
6 changes: 3 additions & 3 deletions docs/reference/release-notes/8.14.1.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,12 +7,12 @@ Also see <<breaking-changes-8.14,Breaking changes in 8.14>>.
[[known-issues-8.14.1]]
[float]
=== Known issues
* When upgrading clusters from version 8.12.2 or earlier, if your cluster contains non-master-eligible nodes,
* When upgrading clusters from version 8.11.4 or earlier, if your cluster contains non-master-eligible nodes,
information about the new functionality of these upgraded nodes may not be registered properly with the master node.
This can lead to some new functionality added since 8.13.0 not being accessible on the upgraded cluster.
This can lead to some new functionality added since 8.12.0 not being accessible on the upgraded cluster.
If your cluster is running on ECK 2.12.1 and above, this may cause problems with finalizing the upgrade.
To resolve this issue, perform a rolling restart on the non-master-eligible nodes once all Elasticsearch nodes
are upgraded.
are upgraded. This issue is fixed in 8.15.0.

[[bug-8.14.1]]
[float]
Expand Down
6 changes: 3 additions & 3 deletions docs/reference/release-notes/8.14.2.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,12 +8,12 @@ Also see <<breaking-changes-8.14,Breaking changes in 8.14>>.
[[known-issues-8.14.2]]
[float]
=== Known issues
* When upgrading clusters from version 8.12.2 or earlier, if your cluster contains non-master-eligible nodes,
* When upgrading clusters from version 8.11.4 or earlier, if your cluster contains non-master-eligible nodes,
information about the new functionality of these upgraded nodes may not be registered properly with the master node.
This can lead to some new functionality added since 8.13.0 not being accessible on the upgraded cluster.
This can lead to some new functionality added since 8.12.0 not being accessible on the upgraded cluster.
If your cluster is running on ECK 2.12.1 and above, this may cause problems with finalizing the upgrade.
To resolve this issue, perform a rolling restart on the non-master-eligible nodes once all Elasticsearch nodes
are upgraded.
are upgraded. This issue is fixed in 8.15.0.

[[bug-8.14.2]]
[float]
Expand Down
Loading