Describe the feature
The tasks distribution only occurs at submission. That means that submitting all tasks at once can lead to have them all running on the same worker in the pool with some worker choice strategies, and any tasks running forever (like an HTTP server) are never reassigned to other workers in the pool given the tasks worker usage.
To fix it, a tasks list with their status need to be added and tasks schedulers using tasks runtime need to be run on a regular basis to redistribute tasks to workers in the pool.
Reactions are currently unavailable
Describe the feature
The tasks distribution only occurs at submission. That means that submitting all tasks at once can lead to have them all running on the same worker in the pool with some worker choice strategies, and any tasks running forever (like an HTTP server) are never reassigned to other workers in the pool given the tasks worker usage.
To fix it, a tasks list with their status need to be added and tasks schedulers using tasks runtime need to be run on a regular basis to redistribute tasks to workers in the pool.