Skip to content

Waterfall policy: make max_task_concurrency optional in rule format - #27

Draft
magniloquency wants to merge 4 commits into
mainfrom
waterfall-optional-max-task-concurrency
Draft

magniloquency wants to merge 4 commits into
mainfrom
waterfall-optional-max-task-concurrency

Conversation

@magniloquency

Copy link
Copy Markdown
Owner

Mirror of finos#833. Base is main; this PR shows only these changes.

Summary

  • When max_task_concurrency is omitted from the CSV policy_content, the rule's field is None and the policy falls back to the value reported by the worker manager heartbeat.
  • An explicit value still acts as a soft cap (min of rule cap and heartbeat cap).
  • Includes a minor style fix: wrap long ternary in waterfall scaling policy.

Test plan

  • Existing test_waterfall_scaling.py tests pass
  • New tests for optional max_task_concurrency pass: rules with and without the field produce correct concurrency limits

When omitted from the CSV policy_content, the rule's max_task_concurrency
is None and the policy falls back to the value reported by the worker
manager heartbeat. An explicit value still acts as a soft cap
(min of rule cap and heartbeat cap).
Signed-off-by: magniloquency <197707854+magniloquency@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant