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 20:03:03 UTC
[jira] [Updated] (AIRFLOW-2763) No precheck mechanism in place
during worker initialisation for the connection to metadata database
[ https://issues.apache.org/jira/browse/AIRFLOW-2763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aizhamal Nurmamat kyzy updated AIRFLOW-2763:
--------------------------------------------
Component/s: (was: worker)
(was: db)
database
> No precheck mechanism in place during worker initialisation for the connection to metadata database
> ---------------------------------------------------------------------------------------------------
>
> Key: AIRFLOW-2763
> URL: https://issues.apache.org/jira/browse/AIRFLOW-2763
> Project: Apache Airflow
> Issue Type: Improvement
> Components: database
> Reporter: Aishwarya Mohan
> Assignee: Aishwarya Mohan
> Priority: Major
> Fix For: 1.10.1
>
>
> Currently when airflow worker is started, no initialization check is in place to see if the connection to metadata database is healthy or not. The worker threads remain alive(after throwing exceptions - OperationalError) leading to a misconception that the worker is up and running the tasks allocated.
> In the case of worker interaction with the broker, a reconnection mechanism exists the exits the worker due to timeout operational error if it failed to establish connection within the configured number of attempts(connection_max_retries).
> An exit/shutdown mechanism needs to be included during worker initialization incase the connection to metadata DB is not established. This will assure the airflow users that the connection to database is in place before they proceed with task scheduling.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)