From 25848c4be7caa65a690ed8d3b31b449702614da0 Mon Sep 17 00:00:00 2001 From: Justin Weissig Date: Tue, 7 May 2019 05:11:36 -0700 Subject: [PATCH] Fixed Typo Fixed typo: schedular/scheduler. --- website/source/guides/advanced-scheduling/affinity.html.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/source/guides/advanced-scheduling/affinity.html.md b/website/source/guides/advanced-scheduling/affinity.html.md index 34108d35b..f35e4fe52 100644 --- a/website/source/guides/advanced-scheduling/affinity.html.md +++ b/website/source/guides/advanced-scheduling/affinity.html.md @@ -120,7 +120,7 @@ job "redis" { } ``` Note that we used the `affinity` stanza and specified `dc2` as the -value for the [attribute][attributes] `${node.datacenter}`. We used the value `100` for the [weight][weight] which will cause the Nomad schedular to rank nodes in datacenter `dc2` with a higher score. Keep in mind that weights can range from -100 to 100, inclusive. Negative weights serve as anti-affinities which cause Nomad to avoid placing allocations on nodes that match the criteria. +value for the [attribute][attributes] `${node.datacenter}`. We used the value `100` for the [weight][weight] which will cause the Nomad scheduler to rank nodes in datacenter `dc2` with a higher score. Keep in mind that weights can range from -100 to 100, inclusive. Negative weights serve as anti-affinities which cause Nomad to avoid placing allocations on nodes that match the criteria. ### Step 3: Register the Job `redis.nomad`