Jarek Potiuk
Jarek Potiuk
> Sure, I can upgrade and check. I believe others here already tested on 2.9.2 reporting the same issue Sometimes similar issues are not the same issues, and upgrading to...
> How can the celery task be marked as failed but the airflow task has a success status? There are few things that happens in celery process AFTER task is...
> We do see a few errors of this kind too, with an Airflow v2.9.2 in Kubernetes + Celery workers + Redis OSS 7.0.7 (AWS Elasticache). Does it help if...
> Unfortunately, in our case we rely on the feature for some DAGs with many sequential tasks, and the tradeoff would not be welcomed by our IT teams (schedule_after_task_execution was...
Do you have proposal to change the behaviour? Opening PR for that would be useful. Airflow has ~2000 contributors so you can become one of them. How do you think...
Yes. I think it should be done like that AIP-44 goal is not to improve performance but increase isolation, so removing of mini-scheduler is likely a good idea.
This it too complex to be completed in the "experimental" phase. For now AIP-44 will have "mini-scheduler" disabled.
> I was wondering if there’s been any recent progress on this issue. This feature would be incredibly helpful for my use case. If things are currently delayed due to...