No longer require master node to install Watcher templates #85287
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jakelandis
added
>bug
:Data Management/Watcher
auto-backport-and-merge
|
Hi @jakelandis, I've created a changelog YAML for you. |
elasticmachine
added
the
Team:Data Management
|
Pinging @elastic/es-data-management (Team:Data Management) |
💚 Backport successful
|
jakelandis
added a commit
to jakelandis/elasticsearch
that referenced
this pull request
Mar 23, 2022
…5287) The master node was required to install Watcher index templates in earlier versions of 7.x to ensure that the master node was aware of composable index templates. When upgrading to 8.x this is no longer an issue since all upgrade paths require elder version of Elasticsearch to be on a version that is aware of composable index templates. This should fix elastic#85043 by ensuring that the watcher history index template is always in place prior to it's intended usage irregardless of the order of which nodes are upgraded.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Mar 23, 2022
…85294) The master node was required to install Watcher index templates in earlier versions of 7.x to ensure that the master node was aware of composable index templates. When upgrading to 8.x this is no longer an issue since all upgrade paths require elder version of Elasticsearch to be on a version that is aware of composable index templates. This should fix #85043 by ensuring that the watcher history index template is always in place prior to it's intended usage irregardless of the order of which nodes are upgraded.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The master node was required to install Watcher index templates
in earlier versions of 7.x to ensure that the master node was aware of
composable index templates.
When upgrading to 8.x this is no longer an issue since all upgrade paths
require elder version of Elasticsearch to be on a version that is aware of
composable index templates.
This should fix #85043 by
ensuring that the watcher history index template is always in place prior
to it's intended usage irregardless of the order of which nodes are upgraded.