You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by "Dan Davydov (JIRA)" <ji...@apache.org> on 2017/01/19 22:07:26 UTC

[jira] [Resolved] (AIRFLOW-680) Making `airflow run` not use a db connection pool

     [ https://issues.apache.org/jira/browse/AIRFLOW-680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Davydov resolved AIRFLOW-680.
---------------------------------
    Resolution: Fixed

> Making `airflow run` not use a db connection pool
> -------------------------------------------------
>
>                 Key: AIRFLOW-680
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-680
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: core
>            Reporter: Dan Davydov
>            Assignee: Dan Davydov
>
> The goal here is to reduce the number of active database sessions on the metadata database. Note that sqla create database connection pools and that when we have thousands of tasks emitting heartbeats it can lead to way too many connections, ultimately maxing out on the MySQL side. #1002 describes the issue.
> (quoted from mistercrunch: https://github.com/apache/incubator-airflow/pull/1021)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)