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

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AIRFLOW-680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15743518#comment-15743518 ] 

ASF subversion and git services commented on AIRFLOW-680:
---------------------------------------------------------

Commit 67ab416dbc6f61095e6e102f44b3825fc482b6c5 in incubator-airflow's branch refs/heads/master from [~pauly]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=67ab416 ]

[AIRFLOW-680] Disable connection pool for commands

This is a continuation of Max's PR here:
https://github.com/apache/incubator-
airflow/pull/1021
We have seen a very substantial DB cpu usage
decrease from this PR (~10x).

This PR was originally created by plypaul I am
just cherrypicking onto master for him.

Testing Done:
- Has been running in Airbnb production for quite
some time (off of a different merge base though)

Closes #1925 from aoen/ddavydov/reduce_db_sessions


> 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)