Where Does Quickwit Store Config and Index Data?
Quickwit reads node config from quickwit.yaml and persists indexes under the data_dir, ./qwdata by default.
Last updated
Quickwit keeps config and data in user-chosen spots. quickwit.yaml sets the data_dir (default ./qwdata), the metastore URI, and the index root; splits, caches, and state accumulate underneath. S3 or Postgres backends move the bulk off local disk.
Local runs therefore back up as two halves: the YAML plus the data_dir tree. Searcher split caches inside data_dir are expendable and rebuild on demand.
Where Quickwit stores this, by platform
./qwdata (Quickwit data_dir, user-chosen)
quickwit.yaml plus data_dir tree (indexes, metastore, split cache). Override with QW_DATA_DIR and QW_METASTORE_URI. Back up YAML and data together.
Frequently asked questions
How do I migrate a Quickwit node?
Copy quickwit.yaml plus the data_dir tree (indexes, metastore) to the new host with matching paths or updated URIs. Object-store indexes only need the config.
How do I move Quickwit data to a larger disk?
Set data_dir in quickwit.yaml (or QW_DATA_DIR) to a bigger disk before indexing. Metastore and index root default underneath it.
Notice an outdated path? Let us know.