From b7dd9f8c29694f47644a700ee0f42444bf8b293c Mon Sep 17 00:00:00 2001 From: M S Vishwanath Bhat Date: Thu, 12 Jul 2018 11:54:48 +0200 Subject: [PATCH] Fix client metadata link in Nomad constraints docs Signed-off-by: M S Vishwanath Bhat --- website/source/docs/job-specification/constraint.html.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/source/docs/job-specification/constraint.html.md b/website/source/docs/job-specification/constraint.html.md index 404dbbd01..423164586 100644 --- a/website/source/docs/job-specification/constraint.html.md +++ b/website/source/docs/job-specification/constraint.html.md @@ -219,7 +219,7 @@ constraint { A potential use case of the `distinct_property` constraint is to spread a service with `count > 1` across racks to minimize correlated failure. Nodes can be annotated with which rack they are on using [client -metadata][client-metadata] with values such as "rack-12-1", "rack-12-2", etc. +metadata][client-meta] with values such as "rack-12-1", "rack-12-2", etc. The following constraint would assure that an individual rack is not running more than 2 instances of the task group.