Users can provide a --preload script to their dask-worker or dask-scheduler commands to launch custom code during execution. This is pragmatic when you want to extend Dask with plugins, but somewhat annoying to do every time.
We might add two entries to the configuration distribued.scheduler.preloads and distributed.worker.preloads that are lists of scripts or imports to pass to the Worker and Scheduler on startup. This should be the default within the worker.py::WorkerBase and scheduler.py::Scheduler constructors.
This was first suggested, I think, by @lesteve
Users can provide a
--preloadscript to their dask-worker or dask-scheduler commands to launch custom code during execution. This is pragmatic when you want to extend Dask with plugins, but somewhat annoying to do every time.We might add two entries to the configuration
distribued.scheduler.preloadsanddistributed.worker.preloadsthat are lists of scripts or imports to pass to the Worker and Scheduler on startup. This should be the default within theworker.py::WorkerBaseandscheduler.py::Schedulerconstructors.This was first suggested, I think, by @lesteve