[
https://issues.apache.org/jira/browse/AIRFLOW-2650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16525583#comment-16525583
]
ASF subversion and git services commented on AIRFLOW-2650:
----------------------------------------------------------
Commit acfc72e01a5dd24a86513ab93e33b8856ad0e284 in incubator-airflow's branch
refs/heads/v1-10-test from [~ashb]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=acfc72e ]
[AIRFLOW-2650] Mark SchedulerJob as succeed when hitting Ctrl-c
Without this fix it turns out that the job would
remain in the running
state.
This also sets things to failed in case of any
other exception.
Closes #3525 from ashb/scheduler-job-status
(cherry picked from commit b0061f1369636c86df87829b93d5ece582591e2a)
Signed-off-by: Bolke de Bruin <[email protected]>
> SchedulerJob is never marked as succeded
> ----------------------------------------
>
> Key: AIRFLOW-2650
> URL: https://issues.apache.org/jira/browse/AIRFLOW-2650
> Project: Apache Airflow
> Issue Type: Bug
> Affects Versions: 1.9.0
> Reporter: Ash Berlin-Taylor
> Priority: Major
> Fix For: 1.10.0
>
>
> The SchedulerJob rows are only ever marked success if {{SchedulerJob.run}}
> finishes cleanly -- this will only happy when max_runs or run_duration is
> specified. Given this is not recommended anymore this means that
> SchedulerJobs are never marked as anything other than running for most
> people. (I have over 400 "running" jobs in my system)
> Noticed by [~jackjack10] in Gitter.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
