You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Bolke de Bruin (JIRA)" <ji...@apache.org> on 2017/12/02 15:24:01 UTC
[jira] [Resolved] (AIRFLOW-1665) Airflow webserver/scheduler don't
handle database disconnects (mysql)
[ https://issues.apache.org/jira/browse/AIRFLOW-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bolke de Bruin resolved AIRFLOW-1665.
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.9.1
Issue resolved by pull request #2822
[https://github.com/apache/incubator-airflow/pull/2822]
> Airflow webserver/scheduler don't handle database disconnects (mysql)
> ---------------------------------------------------------------------
>
> Key: AIRFLOW-1665
> URL: https://issues.apache.org/jira/browse/AIRFLOW-1665
> Project: Apache Airflow
> Issue Type: Bug
> Affects Versions: Airflow 1.8
> Reporter: Vasanth Kumar
> Assignee: Vasanth Kumar
> Labels: database, reconnect
> Fix For: 1.9.1
>
>
> Airflow webserver & scheduler don't handle database disconnects. The process appear to error out and either exit or are left in an off state. This was observed when using mysql.
> I don't see any database reconnect configuration or code.
> Stack tace for scheduler:
> File "...../MySQLdb/connections.py", line 204, in __init__
> super(Connection, self).__init__(*args, **kwargs2)
> sqlalchemy.exc.OperationalError: (_mysql_exceptions.OperationalError) (2002, "Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)")
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)