From 06b5b956b3ba54a1e0a2822014aa0ef941eec8e2 Mon Sep 17 00:00:00 2001 From: Michal Wozniak Date: Mon, 2 Oct 2023 15:04:58 +0200 Subject: [PATCH] PRR Remarks - batching mechanism --- keps/sig-apps/2879-ready-pods-job-status/README.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/keps/sig-apps/2879-ready-pods-job-status/README.md b/keps/sig-apps/2879-ready-pods-job-status/README.md index 5e3a7ba6ac17..897198f1e977 100644 --- a/keps/sig-apps/2879-ready-pods-job-status/README.md +++ b/keps/sig-apps/2879-ready-pods-job-status/README.md @@ -282,8 +282,13 @@ No. - API: PUT Job/status - Estimated throughput: at most one API call for each Job Pod reaching Ready - condition. + Estimated throughput: at most one additional API call for each Job Pod reaching + Ready condition per second. The reason is that the update of the `.status.ready` + field may trigger another reconciliation of the Job. In order to constrain the + number of reconciliations within a second, the Job controller batches and + deduplicates reconciliation requests within a second. In other words, if there + is another reconciliation request planned within a second, the one triggered + by `.status.ready` update is skipped. Originating component: job-controller