Run all host host one by one #4165
Replies: 1 comment 2 replies
-
|
yeah, that makes sense. Right now parallel/limit is batching per task across hosts, so small hosts end up waiting behind the slow ones. What you’re looking for is host-scoped execution: run the full “all” task chain for Host A, then move to Host B, with a concurrency of N hosts at a time (instead of per-step fan-out). If deployer doesn’t support that mode natively, we may need to restructure the workflow (e.g., wrap the “all” sequence into a single per-host task / entrypoint) so parallelism applies to the host “pipeline” rather than each individual step. If you can share how you’re invoking it (command + deploy config snippet), I can suggest the cleanest way to reshape it. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I am working on using deployer to build backups for our docker environment that can be downloaded directly from a server for usage, but I am currently running in to an issue with parallel mode.
I want to run the "all" option for host, but then it does 1 task for all hosts and then goes to the next task and executes it for all hosts, the limit only limits for how many hosts it runs the task.
What I would like to do is have it run all the tasks for one host and then continue on to the next and with parallel/limit change the number of hosts that it is executing at once.
The docker environments are Magento 2 shops and they vary a lot in code and database size, so I can not have all environments running at once for parallel mode and would like to finish up each host instead of having a small host wait a long time for a large host.
Beta Was this translation helpful? Give feedback.
All reactions