[
https://issues.apache.org/jira/browse/AIRFLOW-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16713719#comment-16713719
]
ASF GitHub Bot commented on AIRFLOW-3485:
-----------------------------------------
zzqq1 closed pull request #4297: AIRFLOW-3485
URL: https://github.com/apache/incubator-airflow/pull/4297
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/airflow/models.py b/airflow/models.py
index 74555902a5..4e481f722f 100755
--- a/airflow/models.py
+++ b/airflow/models.py
@@ -1129,6 +1129,7 @@ def generate_command(dag_id,
cmd.extend(["--raw"]) if raw else None
cmd.extend(["-sd", file_path]) if file_path else None
cmd.extend(["--cfg_path", cfg_path]) if cfg_path else None
+ cmd.extend(["&"]) if local and not raw else None
return cmd
@property
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> task rerun after celery worker restart
> --------------------------------------
>
> Key: AIRFLOW-3485
> URL: https://issues.apache.org/jira/browse/AIRFLOW-3485
> Project: Apache Airflow
> Issue Type: Bug
> Components: celery, cli
> Affects Versions: 1.10.1
> Environment: centos7
> Reporter: 曾政
> Assignee: 曾政
> Priority: Critical
> Original Estimate: 12h
> Remaining Estimate: 12h
>
> I find a bug.
> I'm using redis as broker，and using CeleryExecutor as executor。
> step 1:
> force rerun a task that already in success state.
> for example: airflow run dag_id task_name execution_date -A -i --force
> step 2:
> before the task end kill the celery worker (or maybe the worker crash or
> else); and the task is still in running.
> step 3:
> waiting for the task end.
> step 4:
> restart worker and you will find the task will rerun.
>
> I research the problem and find the reason . when killing worker ,the worker
> restore the command to the queue .when the worker restart it read the same
> command and execute it.
> but the normal scheduled task will check its state and ignore the command.
> I find a method to fix it.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
