jscheffl commented on issue #60261: URL: https://github.com/apache/airflow/issues/60261#issuecomment-3746664106
Thanks for the details. Yeah never tested 8 API servers starting at the same time - whereas I'd have assumed migration does not lock for long and might queue for 8x 1s ... interesting that it runs longer and in timeout. So a workaround then is not starting all 8 API server at the same time? Does this help? Yes and agree - then the best approach would be to change the current migration logic from hard coding in the plugin to a real DB migration job. It was only made because at point of first migration the utility was not released as Airflow 3 was not out and later was not possible as Airflow 2 was lagging that feature. As Airflow 2.x support is dropped now, migration could change to "real" DB migration tooling for providers like in FAB. As all versions since Airflow 3 support in edge have not changed DB, actually the full migration can be removed and initial setup for alembic could be added. So any of the volunteers, would be cool to fix this! -- 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]
