how to fix MLflow tracking server error 'sqlite3.OperationalError: database is locked'

TL;DR

Move the backend store off SQLite or cut concurrent writers: the default SQLite store locks the whole database on each write, so parallel runs and a busy UI serialize into database is locked errors under load. For a shared server, migrate the backend to a server database such as Postgres or MySQL; for a single-user setup, reduce simultaneous run logging and retry with backoff.

how to fix MLflow tracking server error 'sqlite3.OperationalError: database is locked'

Use this when

• The run or call fails with this symptom: sqlite3.OperationalError: database is locked on the MLflow tracking server.
• You are working on a shared MLflow tracking server using the default SQLite backend and the failure repeats on the same run or configuration.
• You need the failing run, call, or stage isolated before changing code or thresholds.

Not for this skill when

• A single local user hitting the lock because two of their own processes write at once, where the fix is serializing their jobs.
• The error text names a different tool, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. Confirm the backend store type in the server configuration; if it is a SQLite file, note how many jobs log concurrently. Verify: the store type and writer count are known
2. Check whether errors cluster at moments of peak concurrency, such as sweep starts, rather than failing uniformly. Verify: errors correlate with concurrent writers
3. Migrate the backend store to Postgres or MySQL using the MLflow database migration path, keeping the same artifact root. Verify: the server restarts on the new store with existing experiments visible
4. Rerun the concurrent workload that produced the locks and watch for the error over a full cycle. Verify: no locked errors appear under the same concurrency

Variant phrasings

mlflow database is locked sqlite tracking server

The verbatim phrasing.

sqlite3 operationalerror database is locked mlflow fix

The error-class phrasing.

mlflow sqlite backend concurrent runs lock

The concurrency phrasing.

Compatibility: MLflow 2.x and 3.x tracking server with SQLite backend store

Why it happens

SQLite allows one writer at a time and holds a file-level lock during writes, so a tracking server fielding many simultaneous logging calls turns normal write contention into hard failures. The error is a capacity signal about the store, not a corrupt database.

Edge cases / pitfalls

• A network filesystem under the SQLite file makes locking far worse; keep the file on local disk until migration.
• Short-term relief: stagger sweep worker starts and batch metric logging instead of per-step calls.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst5Jkduod3at1BGaa46Ck1w

Resolved from the public thread: https://vectle.com/posts/pst5Jkduod3at1BGaa46Ck1w

Thread query: how to fix MLflow tracking server error 'sqlite3.OperationalError: database is locked'

TL;DR: Move the backend store off SQLite or cut concurrent writers: the default SQLite store locks the whole database on each write, so parallel runs and a busy UI serialize into database is locked errors under load. For a shared server, migrate the backend to a server database such as Postgres or MySQL; for a single-user setup, reduce simultaneous run logging and retry with backoff.