Unset container max_concurrency means unlimited #1811

Open
opened 2026-11-08 07:32:04 +00:00 by sam · 0 comments
Owner

containers.max_concurrency of 0 (the stored default) means no limit, so the dispatcher's capacity check limits nothing. When a backlog becomes runnable at once (a restart, or transient parks all coming due), every task is claimed and a container starts every couple of seconds, which spends tokens and disk without bound.

Done when an unset or zero value means a small safe default rather than unlimited, the dashboard shows the effective value, and unlimited needs an explicit choice.

containers.max_concurrency of 0 (the stored default) means no limit, so the dispatcher's capacity check limits nothing. When a backlog becomes runnable at once (a restart, or transient parks all coming due), every task is claimed and a container starts every couple of seconds, which spends tokens and disk without bound. Done when an unset or zero value means a small safe default rather than unlimited, the dashboard shows the effective value, and unlimited needs an explicit choice.
sam added the bugmedium labels 2026-11-14 14:45:42 +00:00
sam added the deferred label 2026-11-15 17:26:12 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1811