raise-dispatcher-slots

Raise dispatcher slots to four

Metadata

Statusabandoned
Assignedagent-823
Created2026-07-26T07:11:59.976511220+00:00
Started2026-07-26T07:15:23.602656210+00:00
Failure reasonUser chose to apply the one-line host configuration change directly instead of dispatching a worker.

Description

Operator change

The user explicitly authorized increasing this host's dispatcher concurrency from 2 to 4 so the evaluation backlog and queued configuration work can drain faster.

Use the supported wg config / wg service surface to set the authoritative dispatcher.max_agents to 4 at the currently effective scope and hot-reload the running service. Do not hand-edit graph state, kill existing workers, or change models/profiles. This applies only to this host/project; the earlier Slurm incident was on another host.

Validation

  • wg status and wg service status both report max_agents=4 (or equivalent max=4).
  • The running service hot-reloads without killing the two existing workers.
  • Newly available capacity permits queued work to dispatch.
  • No repository source files are modified.

Depends on

Required by

Log