From cdd25ae6ef43f2b46e4a5327a1991c808dca8431 Mon Sep 17 00:00:00 2001 From: CaoShuFeng Date: Sat, 6 Oct 2018 06:20:55 +0800 Subject: [PATCH] update description about cron jobs (#10183) * update description about cron jobs Fixes: https://github.com/kubernetes/website/issues/10177 * grammar edits --- .../docs/tasks/job/automated-tasks-with-cron-jobs.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/content/en/docs/tasks/job/automated-tasks-with-cron-jobs.md b/content/en/docs/tasks/job/automated-tasks-with-cron-jobs.md index f961bbf34c..015f209ff6 100644 --- a/content/en/docs/tasks/job/automated-tasks-with-cron-jobs.md +++ b/content/en/docs/tasks/job/automated-tasks-with-cron-jobs.md @@ -146,7 +146,15 @@ After the deadline, the cron job does not start the job. Jobs that do not meet their deadline in this way count as failed jobs. If this field is not specified, the jobs have no deadline. -It is important to note that if the `.spec.startingDeadlineSeconds` field is set (not nil), the CronJob controller counts how many missed jobs occurred from the value of `.spec.startingDeadlineSeconds` until now. For example, if it is set to `200`, it counts how many missed schedules occurred in the last 200 seconds. If there were more than 100 missed schedules, the cronjob would not be scheduled. +The CronJob controller counts how many missed schedules happen for a cron job. If there are more than 100 missed +schedules, the cron job is no longer scheduled. When `.spec.startingDeadlineSeconds` is not set, the CronJob +controller counts missed schedules from `status.lastScheduleTime` until now. For example, one cron job is +supposed to run every minute, the `status.lastScheduleTime` of the cronjob is 5:00am, but now it's 7:00am. +That means 120 schedules were missed, so the cron job is no longer scheduled. If the `.spec.startingDeadlineSeconds` +field is set (not null), the CronJob controller counts how many missed jobs occurred from the value of +`.spec.startingDeadlineSeconds` until now. For example, if it is set to `200`, it counts how many missed +schedules occurred in the last 200 seconds. In that case, if there were more than 100 missed schedules in the +last 200 seconds, the cron job is no longer scheduled. ### Concurrency Policy