So yeah hopefully we all agree that if we keep it, we should move it to task.
I guess we can think of this thread as two items: 1. if we keep ability to have tasks not occupy a pool slot, shouldn't it be configured at task level? I think so. 2. but should we keep the ability to have tasks not be considered at task level? 3. if tasks are to stay in pools when deferred, ideally they should do so continuously (e.g. including when in between worker and triggerer) Ok I lied, three items. But 3 is more like a reminder that there is this bad behavior :) Anyway, let's move on to focus on number 2, whether we should provide users a configuration option to make tasks "drop out" of the pool when deferred. After reading your message Jarek, I did not come away with an understanding of a practical use case for having the task vacate the pool slot when deferred. Can you offer an example or two? On Sun, Oct 20, 2024 at 7:29 AM Daniel Standish < daniel.stand...@astronomer.io> wrote: > Totally agree that if we *must* make it configurable, then at task is the > right place. Will read the rest of it later :)
