ldacey commented on issue #23472: URL: https://github.com/apache/airflow/issues/23472#issuecomment-1118564274
Same thing impacted me, likely due to a lot of records and a custom entrypoint. 6,856,476 rows for task_instance 92,682 rows for rendered_task_instance_fields 900,570 rows for dag_run Ultimately, I was able to get things up and running. To do so, here are the steps I took. I would not recommend this, but just in case someone gets stuck like I did. - Installed the patch you mentioned above temporarily - Created a container, navigated to the site-packages airflow folder and then I ran alembic commands one by one using [the migration reference](https://airflow.apache.org/docs/apache-airflow/stable/migrations-ref.html) - I ran into errors during several steps like `Migrate RTIF to use run_id and map_index` due to null `run_id` values and `Add map_index to TaskFail` due to a constraint failure (missing records in `task_instance` table) - I ran `alembic upgrade before:after --sql` commands to generate the raw SQL and then copied, pasted, and executed each command inside of my postgresql container. This allowed me to move forward, but ultimately I had to delete ~85 records from the `task_fail` table which did not exist in the `task_instance` table - This worked, airflow was up and running so I installed apache-airflow==2.3.0 instead of the patch and I was good to go -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
