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

Correct shard allocation filter for watcher example #42602

Merged
merged 1 commit into from
Jun 4, 2019
Merged

Correct shard allocation filter for watcher example #42602

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
6 changes: 3 additions & 3 deletions x-pack/docs/en/watcher/how-watcher-works.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -149,14 +149,14 @@ primary and all replicas of this particular shard will reload.
Because the watches are executed on the node, where the watch shards are, you can create
dedicated watcher nodes by using shard allocation filtering.

You could configure nodes with a dedicated `node.attr.watcher: true` property and
You could configure nodes with a dedicated `node.attr.role: watcher` property and
then configure the `.watches` index like this:

[source,js]
------------------------
PUT .watches/_settings
{
"index.routing.allocation.include": "watcher"
"index.routing.allocation.include.role": "watcher"
}
------------------------
// CONSOLE
Expand Down Expand Up @@ -442,4 +442,4 @@ references the `email_notification_subject` template:
}
}
----------------------------------------------------------------------
// NOTCONSOLE
// NOTCONSOLE