kir-rin commented on issue #66726: URL: https://github.com/apache/airflow/issues/66726#issuecomment-4514846247
Thanks for the detailed report! My suspicion is that this is a SQLite locking issue under concurrent access. In **airflow standalone**, multiple processes (scheduler, api-server, triggerer, etc.) access the same SQLite database. When creating a backfill via API, **the database is locked** error occurs because SQLite doesn't handle concurrent writes well, even with WAL mode. **Notably, is_lock_not_available_error() only recognizes PostgreSQL/MySQL lock errors**, not SQLite's SQLITE_BUSY. Since airflow standalone and SQLite are development-only, one could argue this is expected behavior under concurrent load. -- 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]
