[
https://issues.apache.org/jira/browse/AIRFLOW-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16713656#comment-16713656
]
ASF GitHub Bot commented on AIRFLOW-3485:
-----------------------------------------
zzqq1 opened a new pull request #4297: AIRFLOW-3485
URL: https://github.com/apache/incubator-airflow/pull/4297
Make sure you have checked _all_ steps below.
### Jira
- [ ] My PR addresses the following [Airflow
Jira](https://issues.apache.org/jira/browse/AIRFLOW/) issues and references
them in the PR title. For example, "\[AIRFLOW-XXX\] My Airflow PR"
- https://issues.apache.org/jira/browse/AIRFLOW-XXX
- In case you are fixing a typo in the documentation you can prepend your
commit with \[AIRFLOW-XXX\], code changes always need a Jira issue.
### Description
- [ ] Here are some details about my PR, including screenshots of any UI
changes:
### Tests
- [ ] My PR adds the following unit tests __OR__ does not need testing for
this extremely good reason:
### Commits
- [ ] My commits all reference Jira issues in their subject lines, and I
have squashed multiple commits if they address the same issue. In addition, my
commits follow the guidelines from "[How to write a good git commit
message](http://chris.beams.io/posts/git-commit/)":
1. Subject is separated from body by a blank line
1. Subject is limited to 50 characters (not including Jira issue reference)
1. Subject does not end with a period
1. Subject uses the imperative mood ("add", not "adding")
1. Body wraps at 72 characters
1. Body explains "what" and "why", not "how"
### Documentation
- [ ] In case of new functionality, my PR adds documentation that describes
how to use it.
- When adding new operators/hooks/sensors, the autoclass documentation
generation needs to be added.
- All the public functions and the classes in the PR contain docstrings
that explain what it does
### Code Quality
- [ ] Passes `flake8`
----------------------------------------------------------------
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)
