-
Notifications
You must be signed in to change notification settings - Fork 14.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Graph is empty after update to 2.9.0 on some DAGs #39038
Comments
Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval. |
cc @bbovenzi |
So this only happens to DAGs with Datasets? And it sounds like it happens when we retrieve datasets but either the dataset or task no longer exists so we're pointing to a nonexistent node. Sounds straightforward enough to add a check for that. |
@bbovenzi Yes, that seems to be the case. My guess is this didn't happen before because Airflow was not drawing datasets in the graph |
Apache Airflow version
2.9.0
If "Other Airflow 2 version" selected, which one?
No response
What happened?
Since upgrading from 2.8.3 to 2.9.0, some DAGs are now empty
What you think should happen instead?
Graphs should show in the UI
How to reproduce
Some times when i open the graph it shows for a fraction of a second and then disappears, and other times i see it completely empty; I'm not sure how to reproduce it, but when i open the dev console i see this, which mentions a shape and then names a model that is not part of this dag, which seems even weirder. The dag has a task group if that's relevant:
In case it's relevant, this dag is generated from a single python file that generates dozens of dags from a yaml, not sure if they can somehow be.
An even weirder fact about all this, is that running the same DAG locally using docker-compose, i see the graph just fine, so it's only happening on the hosted version that has exactly the same DAGs and Docker (Maybe some old dag run in the database that had something wrong?)
Operating System
Debian GNU/Linux 12 (bookworm)
Versions of Apache Airflow Providers
apache-airflow-providers-amazon[aiobotocore]==8.20.0
apache-airflow-providers-common-sql==1.12.0
apache-airflow-providers-http==4.10.1
apache-airflow-providers-snowflake==5.4.0
apache-airflow-providers-sqlite==3.7.1
apache-airflow-providers-redis==3.6.1
apache-airflow-providers-celery==3.6.2
Deployment
Other Docker-based deployment
Deployment details
Running on Docker images on AWS ECS
Anything else?
I am willing to submit a PR but i have no idea where/why this happens, and zero knowledge of Airflow's codebase, if someone can at least guide me as to where could i fix this issue
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: