You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Hugo Sousa (JIRA)" <ji...@apache.org> on 2017/04/20 09:45:04 UTC
[jira] [Updated] (AIRFLOW-1130) Airflow 1.8.0 Workers being killed
and started
[ https://issues.apache.org/jira/browse/AIRFLOW-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hugo Sousa updated AIRFLOW-1130:
--------------------------------
Description:
I've updated Airflow 1.7.1.3 to Airflow 1.8 and running Python 2.7.
Since then, there is a log every 30 seconds showing a worker exiting and a new one coming up. Is that an expected behaviour?
Also, there is a deprecation warning from Flask.
Both things can be seen in the screenshot. Just want to make sure this is an expected behaviour before update production with 1.8.
Thank you,
Hugo
was:
I've updated Airflow 1.7.1.3 to Airflow 1.8.
Since then, there is a log every 30 seconds showing a worker exiting and a new one coming up. Is that an expected behaviour?
Also, there is a deprecation warning from Flask.
Both things can be seen in the screenshot. Just want to make sure this is an expected behaviour before update production with 1.8.
Thank you,
Hugo
> Airflow 1.8.0 Workers being killed and started
> ----------------------------------------------
>
> Key: AIRFLOW-1130
> URL: https://issues.apache.org/jira/browse/AIRFLOW-1130
> Project: Apache Airflow
> Issue Type: Task
> Affects Versions: Airflow 1.8
> Reporter: Hugo Sousa
> Priority: Minor
> Attachments: Screen Shot 2017-04-20 at 10.42.29.png
>
>
> I've updated Airflow 1.7.1.3 to Airflow 1.8 and running Python 2.7.
> Since then, there is a log every 30 seconds showing a worker exiting and a new one coming up. Is that an expected behaviour?
> Also, there is a deprecation warning from Flask.
> Both things can be seen in the screenshot. Just want to make sure this is an expected behaviour before update production with 1.8.
> Thank you,
> Hugo
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)