-
Couldn't load subscription status.
- Fork 25.6k
Adding a known issue for watcher during upgrade #127834
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.
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
Adding a known issue for watcher during upgrade #127834
Conversation
|
Pinging @elastic/es-docs (Team:Docs) |
|
Pinging @elastic/es-data-management (Team:Data Management) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
docs/release-notes/known-issues.md
Outdated
| For information about editing your JVM settings, refer to [JVM settings](https://www.elastic.co/docs/reference/elasticsearch/jvm-settings). | ||
| * Users upgrading from an Elasticsearch cluster that had previously been on a version between 7.10.0 and 7.12.1 may see that Watcher will not start on 9.x. The solution is to run the following commands in Kibana Dev Tools: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps mention "or curl"? Up to you though
💚 Backport successful
|
|
@brianseeders should this be added via a changelog yaml file, to avoid being blown away in future? |
|
@leemthompo there's currently no automation around known issues, as I believe that file is completely managed by hand by you folks |
|
Roger that, thank you 👍 |
@brianseeders is this true for 8.x too? |
Watcher can fail to start on upgrade due to an index template conflict. See #127531. This adds it to the 9.0 known issues.