Pieter Hoste

Thanks for the feedback @Luwdo! The questions posed in this issue and in https://github.com/magento/community-features/issues/180 have been thrown together and put into an architectural proposal already, which you can see over...

Nice work! But be aware that the pid files have been removed in the latest version of Magento (version 2.3.3), by https://github.com/magento/magento2/commit/1d9e07b218c7c8ad1f05706828cb2dd47d2d2d58, I think they are now using locking in...

@davidwindell: we do something like this: https://github.com/davidalger/capistrano-magento2/issues/133#issuecomment-537158716 Also messy, but a little bit less messy 🙂 Magento should really implement something easy we can call with the command line, like...

There's a pending PR with a solution for this BTW: https://github.com/magento/magento2/pull/31495 @onlinebizsoft: so far we haven't seen big issues with this new solution (which we've patched into some of our...

Thanks for the feedback @nuzil! 1. I saw it as those two new options being used simultaneous to resolve the problem, only the `--max-idle-time` wouldn't resolve it by itself indeed....

> Yep, I would recommend just disable jobs you dont need. We can't just disable those consumers if there is a chance those async features will be used someday. Suppose...

Ok thanks for the further explanation! 1. I think you are more talking about https://github.com/magento/community-features/issues/181 here, let's not confuse these two feature requests, they are completely different :) 2. I'm...

@nuzil: thought about it for a bit more, since these new options I was suggesting would be optional and configurable, do you still have objections against them? And we could...

We can probably close this PR since https://github.com/magento/magento-composer-installer/commit/50318ac49b6121645bdff5e866c3369e73d42f7c#diff-d2ab9925cad7eac58e0ff4cc0d251a937ecf49e4b6bf57f8b95aab76648a9d34 was released in [0.2.0](https://github.com/magento/magento-composer-installer/releases/tag/0.2.0) Thanks for the effort @fooman!

Looks like my last remark eventually got fixed in https://github.com/magento/devdocs/commit/3c7a6ad7df8b7b9cdac19e1f1e52218f24e212b1 Let's close this issue now finally.