Skip to content
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

Handle IntegrityError while creating TIs #10136

Merged
merged 4 commits into from
Aug 7, 2020
Merged

Conversation

msumit
Copy link
Contributor

@msumit msumit commented Aug 3, 2020

Background
While doing a trigger_dag from UI, DagRun gets created first and then webserver starts creating TIs. Meanwhile, Scheduler also picks up the DagRun and starts creating the TIs, which results in IntegrityError as the Primary key constraint gets violated. This happens when a DAG has a good number of tasks (500+).

Also, changing the TIs array with a set for faster lookups.

@msumit
Copy link
Contributor Author

msumit commented Aug 7, 2020

@ashb @kaxil @mik-laj @potiuk PTAL

session.commit()
except IntegrityError as err:
self.log.info(str(err))
self.log.info(f'Hit IntegrityError while creating the TIs for '
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit

Suggested change
self.log.info(f'Hit IntegrityError while creating the TIs for '
self.log.info('Hit IntegrityError while creating the TIs for '

@msumit msumit merged commit 2102122 into apache:master Aug 7, 2020
@kaxil kaxil added this to the Airflow 1.10.12 milestone Aug 7, 2020
kaxil pushed a commit that referenced this pull request Aug 14, 2020
While doing a trigger_dag from UI, DagRun gets created first and then WebServer starts creating TIs. Meanwhile, Scheduler also picks up the DagRun and starts creating the TIs, which results in IntegrityError as the Primary key constraint gets violated. This happens when a DAG has a good number of tasks.

Also, changing the TIs array with a set for faster lookups for Dags with too many tasks.

(cherry picked from commit 2102122)
kaxil pushed a commit that referenced this pull request Aug 15, 2020
While doing a trigger_dag from UI, DagRun gets created first and then WebServer starts creating TIs. Meanwhile, Scheduler also picks up the DagRun and starts creating the TIs, which results in IntegrityError as the Primary key constraint gets violated. This happens when a DAG has a good number of tasks.

Also, changing the TIs array with a set for faster lookups for Dags with too many tasks.

(cherry picked from commit 2102122)
kaxil pushed a commit that referenced this pull request Aug 15, 2020
While doing a trigger_dag from UI, DagRun gets created first and then WebServer starts creating TIs. Meanwhile, Scheduler also picks up the DagRun and starts creating the TIs, which results in IntegrityError as the Primary key constraint gets violated. This happens when a DAG has a good number of tasks.

Also, changing the TIs array with a set for faster lookups for Dags with too many tasks.

(cherry picked from commit 2102122)
msumit added a commit to twitter-forks/airflow that referenced this pull request Sep 4, 2020
While doing a trigger_dag from UI, DagRun gets created first and then WebServer starts creating TIs. Meanwhile, Scheduler also picks up the DagRun and starts creating the TIs, which results in IntegrityError as the Primary key constraint gets violated. This happens when a DAG has a good number of tasks.

Also, changing the TIs array with a set for faster lookups for Dags with too many tasks.
cfei18 pushed a commit to cfei18/incubator-airflow that referenced this pull request Mar 5, 2021
While doing a trigger_dag from UI, DagRun gets created first and then WebServer starts creating TIs. Meanwhile, Scheduler also picks up the DagRun and starts creating the TIs, which results in IntegrityError as the Primary key constraint gets violated. This happens when a DAG has a good number of tasks.

Also, changing the TIs array with a set for faster lookups for Dags with too many tasks.

(cherry picked from commit 2102122)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants