@dmcg Welcome to Discourse, and thanks for creating the issue!
Since this is related to Understanding Work Stealing, I think we can continue this discussion there.
To close the loop on this topic:
- we need to use
distributed.scheduler.work-stealing
here, and - setting the config values using the config file or environment variables is recommended (because some config values are set only during scheduler start-up)