[airflow] branch main updated: Executor events are not always "exited" here (#30859)

[ur...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

uranusjr pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git


The following commit(s) were added to refs/heads/main by this push:
     new f39ccad9d8 Executor events are not always "exited" here (#30859)
f39ccad9d8 is described below

commit f39ccad9d8fa239bdbeb7e88afdedea5e8fddf76
Author: Daniel Standish <15...@users.noreply.github.com>
AuthorDate: Wed May 10 00:01:19 2023 -0700

    Executor events are not always "exited" here (#30859)
---
 airflow/jobs/scheduler_job_runner.py | 9 +--------
 1 file changed, 1 insertion(+), 8 deletions(-)

diff --git a/airflow/jobs/scheduler_job_runner.py b/airflow/jobs/scheduler_job_runner.py
index c7088412de..d98b8968bd 100644
--- a/airflow/jobs/scheduler_job_runner.py
+++ b/airflow/jobs/scheduler_job_runner.py
@@ -704,14 +704,7 @@ class SchedulerJobRunner(BaseJobRunner, LoggingMixin):
             # We create map (dag_id, task_id, execution_date) -> in-memory try_number
             ti_primary_key_to_try_number_map[ti_key.primary] = ti_key.try_number
 
-            self.log.info(
-                "Executor reports execution of %s.%s run_id=%s exited with status %s for try_number %s",
-                ti_key.dag_id,
-                ti_key.task_id,
-                ti_key.run_id,
-                state,
-                ti_key.try_number,
-            )
+            self.log.info("Received executor event with state %s for task instance %s", state, ti_key)
             if state in (State.FAILED, State.SUCCESS, State.QUEUED):
                 tis_with_right_state.append(ti_key)