[ 
https://issues.apache.org/jira/browse/AIRFLOW-5071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17243148#comment-17243148
 ] 

ASF GitHub Bot commented on AIRFLOW-5071:
-----------------------------------------

nathadfield edited a comment on issue #10790:
URL: https://github.com/apache/airflow/issues/10790#issuecomment-737899403


   Not sure if this is relevant but, when the task was rescheduled five minutes 
later, I saw this.
   
   ```
   [2020-12-03 11:57:07,266] {scheduler_job.py:1237} ERROR - Executor reports 
task instance <TaskInstance: target_dag.wait-task 2020-12-02 00:00:00+00:00 
[queued]> finished (success) although the task says its queued. (Info: None) 
Was the task killed externally?
   Process ForkProcess-34:
   Traceback (most recent call last):
     File "/usr/local/lib/python3.7/multiprocessing/process.py", line 297, in 
_bootstrap
       self.run()
     File "/usr/local/lib/python3.7/multiprocessing/process.py", line 99, in run
       self._target(*self._args, **self._kwargs)
     File 
"/usr/local/lib/python3.7/site-packages/airflow/utils/dag_processing.py", line 
365, in _run_processor_manager
       processor_manager.start()
     File 
"/usr/local/lib/python3.7/site-packages/airflow/utils/dag_processing.py", line 
596, in start
       return self._run_parsing_loop()
     File 
"/usr/local/lib/python3.7/site-packages/airflow/utils/dag_processing.py", line 
659, in _run_parsing_loop
       self._processors.pop(processor.file_path)
   KeyError: '/usr/local/airflow/dags/target_dag.py'
   [2020-12-03 11:57:09,101] {dag_processing.py:399} WARNING - 
DagFileProcessorManager (PID=157) exited with exit code 1 - re-launching
   [2020-12-03 11:57:09,105] {dag_processing.py:250} INFO - Launched 
DagFileProcessorManager with pid: 33432
   ```


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


> Thousand os Executor reports task instance X finished (success) although the 
> task says its queued. Was the task killed externally?
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AIRFLOW-5071
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-5071
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: DAG, scheduler
>    Affects Versions: 1.10.3
>            Reporter: msempere
>            Priority: Critical
>             Fix For: 1.10.12
>
>         Attachments: image-2020-01-27-18-10-29-124.png, 
> image-2020-07-08-07-58-42-972.png
>
>
> I'm opening this issue because since I update to 1.10.3 I'm seeing thousands 
> of daily messages like the following in the logs:
>  
> ```
>  {{__init__.py:1580}} ERROR - Executor reports task instance <TaskInstance: X 
> 2019-07-29 00:00:00+00:00 [queued]> finished (success) although the task says 
> its queued. Was the task killed externally?
> {{jobs.py:1484}} ERROR - Executor reports task instance <TaskInstance: X 
> 2019-07-29 00:00:00+00:00 [queued]> finished (success) although the task says 
> its queued. Was the task killed externally?
> ```
> -And looks like this is triggering also thousand of daily emails because the 
> flag to send email in case of failure is set to True.-
> I have Airflow setup to use Celery and Redis as a backend queue service.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to