Skip to content

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.

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

Merged
merged 2 commits into from
May 7, 2025
Merged

Adding a known issue for watcher during upgrade #127834

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
df91d5c
Adding a known issue for watcher during upgrade
masseyke May 7, 2025
b473fb1
mentioning curl
masseyke May 7, 2025
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/release-notes/known-issues.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,3 +27,10 @@ This issue will be fixed in a future patch release (see [PR #126990](https://git
```

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:
Copy link
Member

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

```
DELETE _index_template/.triggered_watches
DELETE _index_template/.watches
POST /_watcher/_start
```
Loading