jscheffl opened a new pull request, #36518:
URL: https://github.com/apache/airflow/pull/36518
Removes the "Set to state 'running'" option from UI for Task instances. If
users are using this, immediately an "Zombie task" error like the following is
produced in the task logs:
```
[2023-12-31, 18:57:01 CET] {scheduler_job_runner.py:1766} ERROR - Detected
zombie job: {'full_filepath':
'/opt/airflow/airflow/example_dags/example_params_ui_tutorial.py',
'processor_subdir': '/files/dags', 'msg': "{'DAG Id':
'example_params_ui_tutorial', 'Task Id': 'show_params', 'Run Id':
'manual__2023-12-31T18:56:01+01:00', 'Hostname': 'c01bb381ee62', 'External
Executor Id': '0464fee6-8ba2-4a3b-87cc-f9c0d891bfa9'}", 'simple_task_instance':
<airflow.models.taskinstance.SimpleTaskInstance object at 0x7f8ac6c4b6a0>,
'is_failure_callback': True} (See
https://airflow.apache.org/docs/apache-airflow/stable/core-concepts/tasks.html#zombie-undead-tasks)
```
See also
https://airflow.apache.org/docs/apache-airflow/stable/core-concepts/tasks.html#zombie-undead-tasks
Reason for removal is that the setting to state "running" just creates an
inconsistent state in the meta database, no background activity is started. For
advanced user who know what they are doing, rather the API `HTTP PATCH
/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances/{task_id}' is the right way.
But we should not leave a standard option in the normal user UI as this is
mis-leading.
closes: #35729
--
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.
To unsubscribe, e-mail: commits-unsubscr...@airflow.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
