GitHub user devgonvarun created a discussion: Manual triggers picked by 
scheduler with delay

### Apache Airflow version

main (development)

### If "Other Airflow 2/3 version" selected, which one?

3.1.1

### What happened?

There is always a delay of around 2 minutes between manual dag triggers from UI 
and scheduler picking up the dag despite only a configured heartbeat of 2s. 
KubernetesExecutor. On dag trigger the dag goes into Queued state and changes 
to Running state once the worker pod is spawned. The task is still queued at 
this point until the worker pod gets into the running state. But it takes 2 
minutes for the worker pod to spawn. 

### What you think should happen instead?

Scheduler should not have large delays to spawn worker pod. 

### How to reproduce

Airflow in kubernetes installation. with KubernetesExecutor. Trigger a dag 
manually from the UI. 

### Operating System

Debian GNU/Linux 12 (bookworm)

### Versions of Apache Airflow Providers

_No response_

### Deployment

Official Apache Airflow Helm Chart

### Deployment details

_No response_

### Anything else?

_No response_

### Are you willing to submit PR?

- [ ] Yes I am willing to submit a PR!

### Code of Conduct

- [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)


GitHub link: https://github.com/apache/airflow/discussions/59526

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]

Reply via email to