Skip to content

After upgrading to 2.5.3, Dag Processing time increased dramatically. #30593

@wookiist

Description

@wookiist

Apache Airflow version

2.5.3

What happened

I upgraded my airflow cluster from 2.5.2 to 2.5.3 , after which strange things started happening.
I'm currently using a standalone dagProcessor, and the parsing time that used to take about 2 seconds has suddenly increased to about 10 seconds.
I'm thinking it's weird because I haven't made any changes other than a version up, but is there something I can look into? Thanks in advance! 🙇🏼
image

What you think should happen instead

I believe that the time it takes to parse a Dag should be constant, or at least have some variability, but shouldn't take as long as it does now.

How to reproduce

If you cherrypick this commit into 2.5.2 stable code, the issue will recur.

Operating System

Debian GNU/Linux 11 (bullseye)

Versions of Apache Airflow Providers

No response

Deployment

Official Apache Airflow Helm Chart

Deployment details

  • Kubernetes 1.21 Cluster
  • 1.7.0 helm chart
  • standalone dag processor
  • using kubernetes executor
  • using mysql database

Anything else

This issue still persists, and restarting the Dag Processor has not resolved the issue.

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions