quickwit-oss / quickwit-oss/quickwit
migration problem
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
image version: quickwit/quickwit@sha256:6c2e01ab6fd95b90f880c0ced29e4057878d470810e86c1b5de75f36d0c6037c
After a restart we have this log:
2026-02-24T14:54:46.377Z ERROR run_migrations: quickwit_metastore::metastore::postgres::migrator: failed to run PostgreSQL migrations error=migration 25 was previously applied but is missing in the resolved migrations
2026-02-24T14:54:46.724Z ERROR quickwit: command failed error=failed to resolve metastore uri postgresql://quickwit:***redacted***@pg-quickwit-rw
✘ command failed: failed to resolve metastore uri postgresql://quickwit:***redacted***@pg-quickwit-rw
Caused by:
0: failed to connect to metastore: internal error: failed to run PostgreSQL migrations; cause: migration 25 was previously applied but is missing in the resolved migrations``
1: internal error: failed to run PostgreSQL migrations; cause: migration 25 was previously applied but is missing in the resolved migrations
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the quickwit_metastore::metastore::postgres::migrator entry point and the logged failure for migration 25. Inspect how PostgreSQL migrations are resolved and applied; done means a restart no longer reports migration 25 as previously applied but missing from the resolved migrations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, rust
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100