We are currently intending to turn on scheduler-side queuing by default. This will give much better cluster memory use in most cases, and help users avoid the painful "running out of memory on simple workloads" experience #2602.
It does slow things down, but the increased stability and better out-of-the-box user experience seems worthwhile.
Specifically, this will mean changing the default worker-saturation value from inf to 1.0 or 1.1 or something. Advanced users who need to keep old behavior can get it back by changing this config, which will be documented #7203.
TODO:
We are currently intending to turn on scheduler-side queuing by default. This will give much better cluster memory use in most cases, and help users avoid the painful "running out of memory on simple workloads" experience #2602.
It does slow things down, but the increased stability and better out-of-the-box user experience seems worthwhile.
Specifically, this will mean changing the default
worker-saturationvalue frominfto1.0or1.1or something. Advanced users who need to keep old behavior can get it back by changing this config, which will be documented #7203.TODO:
decide_worker_rootish_queuing_disabledassertion fails when retiring worker #7063AssertionError: waiting on released depwhen worker-saturation < .inf #7204secede#7223decide_workercould be expensive on large clusters with queuing enabled #7246test_nested_compute#7247