From 64f35f9cf37629ba4252aa8b1f66c0d2f87f3590 Mon Sep 17 00:00:00 2001 From: Seth Hoenig Date: Thu, 7 Jul 2022 16:46:26 -0500 Subject: [PATCH] docs: move upgrade docs for max_client_timeout Co-authored-by: Luiz Aoqui --- website/content/docs/upgrade/upgrade-specific.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/website/content/docs/upgrade/upgrade-specific.mdx b/website/content/docs/upgrade/upgrade-specific.mdx index 6bb5dd199..2e97064ab 100644 --- a/website/content/docs/upgrade/upgrade-specific.mdx +++ b/website/content/docs/upgrade/upgrade-specific.mdx @@ -32,10 +32,12 @@ to version 3, and in Nomad 1.4.0 Nomad requires the use of raft protocol version 3. If [`raft_protocol`] version is explicitly set, it must now be set to `3`. For more information see the [Upgrading to Raft Protocol 3] guide. +## Nomad 1.3.2, 1.2.9, 1.1.15 + #### Client `max_kill_timeout` now enforced Nomad versions since v0.9 have incorrectly ignored the Client [`max_kill_timeout`][max_kill_timeout] -configuration option. This bug has been fixed in Nomad versions v1.4.0, v.1.3.2, +configuration option. This bug has been fixed in Nomad versions v.1.3.2, v1.2.9, and v1.1.15. Job submitters should be aware that a Task's [`kill_timeout`][kill_timeout] will be reduced to the Client's `max_kill_timeout` if the value exceeds the maximum.