airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeffrey Bian (JIRA)" <>
Subject [jira] [Commented] (AIRFLOW-1559) MySQL warnings about aborted connections, missing engine disposal
Date Fri, 20 Oct 2017 18:19:00 GMT


Jeffrey Bian commented on AIRFLOW-1559:

Proposed fix:

At the beginning of the *helper* function, because the engine will be a 'copy' in the subprocess,
need to close them explicitly first and let the subsequent function implicitly recreate the
resource via import settings etc.

Then at the end of the function, do another round of 



> MySQL warnings about aborted connections, missing engine disposal
> -----------------------------------------------------------------
>                 Key: AIRFLOW-1559
>                 URL:
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: db
>            Reporter: Daniel Huang
>            Priority: Minor
> We're seeing a flood of warnings about aborted connections in our MySQL logs. 
> {code}
> Aborted connection 56720 to db: 'airflow' user: 'foo' host: 'x.x.x.x' (Got an error reading
communication packets)
> {code}
> It appears this is because we're not performing [engine disposal|].
The most common source of this warning is from the scheduler, when it kicks off new processes
to process the DAG files. Calling dispose in
greatly reduced these messages. However, the worker is still causing some of these, I assume
from when we spin up processes to run tasks. We do call dispose in,
but I think it's a bit early. Not sure if there's a place we can put this cleanup to ensure
it's done everywhere.
> Quick script to reproduce this warning message:
> {code}
> from airflow import settings
> from airflow.models import Connection
> session = settings.Session()
> session.query(Connection).count()
> session.close()
> # not calling settings.engine.dispose()
> {code}
> Reproduced with Airflow 1.8.1, MySQL 5.7, and SQLAlchemy 1.1.13. 

This message was sent by Atlassian JIRA

View raw message