From 0f8f581efc7fcb5f778bd16f1513ee780a1eae69 Mon Sep 17 00:00:00 2001 From: Preetha Appan <460133+preetapan@users.noreply.github.com> Date: Tue, 8 Oct 2019 10:08:27 -0500 Subject: [PATCH] clarify version for new gc config in server stanza --- website/source/docs/configuration/server.html.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/website/source/docs/configuration/server.html.md b/website/source/docs/configuration/server.html.md index 0431c784f..2c153c9b1 100644 --- a/website/source/docs/configuration/server.html.md +++ b/website/source/docs/configuration/server.html.md @@ -83,7 +83,8 @@ server { frequent but smaller collections. Raising the interval will perform collections less frequently but collect more jobs at a time. Reducing this interval is useful if there is a large throughput of tasks, leading to a large set of - dead jobs. This is specified using a label suffix like "30s" or "3m". + dead jobs. This is specified using a label suffix like "30s" or "3m". `job_gc_interval` + was introduced in Nomad 0.10.0. - `job_gc_threshold` `(string: "4h")` - Specifies the minimum time a job must be in the terminal state before it is eligible for garbage collection. This is