ChunkManager Operations
Use these pages to operate the .firecube/ control plane for one product.
ChunkManager commands inspect and change product-local run history, span
records, write claims, snapshots, and cleanup state.
Command Groups
| Command group | Use it for |
|---|---|
firecube chunks list |
Inspect ChunkManager records and span coverage. |
firecube chunks runs |
Inspect or abandon ingestion runs. |
firecube chunks claims |
Inspect or clear write-coordination claims. |
firecube chunks delete |
Delete tracked records and, when configured, storage data. |
firecube chunks delete-span |
Delete storage chunks described by span records. |
firecube chunks snapshots |
Check or rebuild snapshot read models. |
Product URI
Pass the full product URI with --product:
Expected output resembles:
Product Key Type Size (MB) Date
-----------------------------------------------------------------------
product.zarr span_<run>_batch_0001... span 0.0 2026-06-03 ...
product.zarr span_<run>_batch_0000... span 0.0 2026-06-03 ...
Summary: 3 chunks, 0.0 MB total
firecube chunks may also print storage-configuration log lines when logging
is enabled. The command result is the table or JSON payload.
Local Storage Preflight
Commands that delete storage data need a storage config that points at the same local root as the product:
export FIRECUBE_STORAGE_TYPE=local
export FIRECUBE_STORAGE_DRIVER=fsspec
export FIRECUBE_TARGET_PATH=/data/products
If FIRECUBE_TARGET_PATH is missing, a local chunks delete dry-run can work
while the real storage deletion cannot locate the local base path.
Next Steps
- Inspect ChunkManager State — list records, runs, claims, or snapshots
- Recover Runs And Claims — recover a stuck run or stale claim
- Delete And Reingest — run cleanup or reingestion workflows
- Snapshots — rebuild fast listings for chunk-manager commands