jscheffl commented on issue #60261: URL: https://github.com/apache/airflow/issues/60261#issuecomment-3740333928
So before raising a fix we need to triage the root cause to fix it on the "right level". If you receive the lock timeout error I suspect the API extension for Edge is not starting up, means it is not active. This means if the Edge worker calls the backend then there is just the API endpoint missing. FastAPI responds with a HTTP 405 signalling that the "method not allowed" == there is no API endpoint. Unfortunately HTTP 405 seems to be the default instead of a HTTP 404 (Not Found). So probably we need to things: 1. Improved Error Handling - respond on HTTP 405 to log the same error as if HTTP 404 is hit 2. Understand the root cause of the DB Locking issue. Might also be a permission limit in Airflow. More logs are needed. Then the startup of UI Plugin should be improved to either fix the problem or if un-critical (I assume/remember the locking is only used when migration is needed - assuming no migration needed) then skip the problem and continue with a warning. Before raising a fix, I see you use Edge 1.4.0 - can you please upgrade to Edge 2.0.1 and also to most recent patch version of Airflow and reproduce? -- 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]
