docs(scheduler): parjob bucket-reset comment describes the job-level .host want after bug-1883
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
3c446bef3f
commit
1fb1bcc971
1 changed files with 2 additions and 1 deletions
|
|
@ -460,7 +460,8 @@ static int parjob_try_plan_(xce_sched_core_t* core, xce_sched_ctx_t* ctx,
|
|||
* see host_iter.c's own file header). Left un-reset, it would
|
||||
* still carry a DIFFERENT bucket's want (or, for the very first
|
||||
* bucket ever tried, the job-level ctx->worker==NULL prepare
|
||||
* pass's own dead-write into .host) -- harmless for seqjob
|
||||
* pass's whole-primary slots:maxTasks want, which that pass
|
||||
* rebuilds per primary since bug-1883) -- harmless for seqjob
|
||||
* (nslots is always 1, so every bucket's want is identical by
|
||||
* construction) but actively wrong for parjob, where bucket size
|
||||
* genuinely varies call to call: a stale want here can wrongly
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue