[GitHub] [airflow] arjunanan6 commented on issue #32674: Airflow migrations taking too long

["arjunanan6 (via GitHub)" <gi...@apache.org>]

arjunanan6 commented on issue #32674:
URL: https://github.com/apache/airflow/issues/32674#issuecomment-1641468376

   No, a cleanup has not been done since a while - mainly because we want to preserve the task run history. The task run history must be quite big now, I can check exactly what the state is shortly. 
   
   >Do you have any worker/scheduler/triggerer running during the migration? if so, they could lock some rows in different tables which blocks the migration
   
   Yes, we do. There is an active airflow deployment in place that is operating normally and a helm upgrade is only done in 2 situations: a) We introduce a new dag/fixes to existing DAGs, or b) An airflow version upgrade. I looked quickly at our pgbouncer logs to see if there was anything significant going on around the time of the upgrade but did not immediately spot anything. 
   
   I suppose a bandaid fix would be to set these two to false:
   webserver.waitForMigrations.enabled
   scheduler.waitForMigrations.enabled
   
   But this would only hide the problem. 


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org