You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Aizhamal Nurmamat kyzy (JIRA)" <ji...@apache.org> on 2019/05/17 22:19:03 UTC
[jira] [Updated] (AIRFLOW-2371) SubdagOperator ignores pooling
[ https://issues.apache.org/jira/browse/AIRFLOW-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aizhamal Nurmamat kyzy updated AIRFLOW-2371:
--------------------------------------------
Labels: subdag (was: )
Component/s: operators
Adding 'operators' component and 'subdag' label for component refactor.
> SubdagOperator ignores pooling
> ------------------------------
>
> Key: AIRFLOW-2371
> URL: https://issues.apache.org/jira/browse/AIRFLOW-2371
> Project: Apache Airflow
> Issue Type: Bug
> Components: operators, subdag
> Affects Versions: 1.9.0
> Environment: Airflow 1.9.0
> Reporter: Xiao Zhu
> Priority: Major
> Labels: subdag
>
> Basically we need a long term solution for https://issues.apache.org/jira/browse/AIRFLOW-74 . Using SequentialExecutor is a workaround, however it slows down execution of subdags.
> Looking for a better solution.
> I also see that when running subdags, db connection pools are not shared either (since they are separate processes), which causes db disconnection issues like https://issues.apache.org/jira/browse/AIRFLOW-2340 on our db because there can be too many connections. I hope it can be fixed too when subdag operator works with pooling..
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)