From 58ea294f0b015d317a589a37b5be5087debb58bb Mon Sep 17 00:00:00 2001 From: James Rasell Date: Fri, 1 Nov 2024 14:54:51 +0000 Subject: [PATCH] docs: add note to reschedule block for update progress deadline. (#24346) Co-authored-by: Aimee Ukasick --- website/content/docs/job-specification/reschedule.mdx | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/website/content/docs/job-specification/reschedule.mdx b/website/content/docs/job-specification/reschedule.mdx index 97545b2e4..dfdf1ed52 100644 --- a/website/content/docs/job-specification/reschedule.mdx +++ b/website/content/docs/job-specification/reschedule.mdx @@ -78,8 +78,10 @@ they run on every node. - `max_delay` `(string: )` - is an upper bound on the delay beyond which it will not increase. This parameter is used when `delay_function` is `exponential` or `fibonacci`, and is ignored when `constant` delay is used. -- `unlimited` `(boolean:)` - `unlimited` enables unlimited reschedule attempts. If this is set to true - the `attempts` and `interval` fields are not used. +- `unlimited` `(boolean:)` - `unlimited` enables unlimited reschedule attempts. If this is + set to `true` the `attempts` and `interval` fields are not used. The [`progress_deadline`][] + parameter within the update block is still adhered to when this is set to `true`, meaning no more + reschedule attempts are triggered once the [`progress_deadline`][] is reached. Information about reschedule attempts are displayed in the CLI and API for allocations. Rescheduling is enabled by default for service and batch jobs @@ -127,3 +129,5 @@ job "docs" { } } ``` + +[`progress_deadline`]: /nomad/docs/job-specification/update#progress_deadline