From 7a587d25ae6c0f9cb13dd508d40685d08c12c1f7 Mon Sep 17 00:00:00 2001 From: Chris Cho Date: Wed, 5 Jun 2019 01:28:58 +0900 Subject: [PATCH] Change shard allocation filter property and api (#42602) The current example is not working and a bit confused. This change tries to match it with the sample of the watcher blog. --- x-pack/docs/en/watcher/how-watcher-works.asciidoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/x-pack/docs/en/watcher/how-watcher-works.asciidoc b/x-pack/docs/en/watcher/how-watcher-works.asciidoc index 80aeb69a38d5b..5ecc5b41ec61c 100644 --- a/x-pack/docs/en/watcher/how-watcher-works.asciidoc +++ b/x-pack/docs/en/watcher/how-watcher-works.asciidoc @@ -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 @@ -442,4 +442,4 @@ references the `email_notification_subject` template: } } ---------------------------------------------------------------------- -// NOTCONSOLE \ No newline at end of file +// NOTCONSOLE