influxdata/influxdb · critical · PersisterError

snapshot manifest parse task panicked

Error message

snapshot manifest parse task panicked: {0}

What it means

PersisterError::SnapshotParseTaskFailed indicates that a spawned tokio task responsible for parsing a snapshot manifest panicked. The JoinError from joining the task is attached as the `#[source]` and rendered into the message.

Solutions

1. Inspect the JoinError panic message to find the failing line in the manifest parse task.
2. Validate/repair or remove the corrupt snapshot manifest in the object store so a fresh one can be written.
3. Ensure influxdb3 versions are consistent across the deployment (manifest format compatibility).
4. Report/upgrade if the panic originates in influxdb3 parsing code.

Example fix

// before: unwrap on potentially malformed manifest entry
let db = manifest.databases.get(db_name).unwrap();
// after
let db = manifest.databases.get(db_name)
    .ok_or_else(|| anyhow!("database {db_name} missing from snapshot manifest"))?;

fn is_manifest_parse_panic(e: &PersisterError) -> bool {
    matches!(e, PersisterError::SnapshotParseTaskFailed(_))
}

match persister.load_snapshot(...).await {
    Err(PersisterError::SnapshotParseTaskFailed(join)) => {
        eprintln!("manifest parse task panicked: {join}");
        // fall back to the last known-good snapshot manifest
    }
    Err(e) => return Err(e.into()),
    Ok(v) => v,
}

When it happens

Trigger: Awaiting a `tokio::spawn`ed snapshot-manifest parse task whose body panicked — e.g. unwrap on malformed manifest JSON, invalid deserialized structure, or index out of range while walking the manifest.

Common situations: Corrupt or partially-written snapshot manifests in object storage causing unwraps to fail; version mismatch where an old manifest shape trips parsing logic; bugs in the parse task itself.

Related errors

• table snapshot persistence task panicked
• start watchdog thread
• Table snapshot persistence task failed
• blocking task join
• column id in series key should be valid

AI-assisted analysis of influxdata/influxdb@06200ef96b (2026-09-19). Data as JSON: /api/errors/a70d68bdf66feafb. Report an issue: GitHub.

Appendix: source

Thrown at influxdb3_write/src/persister.rs:74

    #[error("object_store error: {0}")]
    ObjectStore(#[from] object_store::Error),

    #[error("parquet error: {0}")]
    ParquetError(#[from] parquet::errors::ParquetError),

    #[error("tried to serialize a parquet file with no rows")]
    NoRows,

    #[error("parse int error: {0}")]
    ParseInt(#[from] std::num::ParseIntError),

    #[error("unexpected persister error: {0:?}")]
    Unexpected(#[from] anyhow::Error),

    #[error("table snapshot persistence task panicked: {0}")]
    TableSnapshotPersistenceTaskFailed(#[source] tokio::task::JoinError),

    #[error("snapshot manifest parse task panicked: {0}")]
    SnapshotParseTaskFailed(#[source] tokio::task::JoinError),

    #[error("table index error: {0}")]
    TableIndexPathError(#[source] crate::paths::PathError),

    #[error("object meta is missing filename")]
    MissingFilename,

    #[error("failed to parse snapshot sequence number from filename")]
    InvalidSnapshotSequenceNumber,
}

impl From<PersisterError> for DataFusionError {
    fn from(error: PersisterError) -> Self {
        match error {
            PersisterError::DataFusion(e) => e,
            PersisterError::ObjectStore(e) => DataFusionError::ObjectStore(Box::new(e)),
            PersisterError::ParquetError(e) => DataFusionError::ParquetError(Box::new(e)),

View on GitHub (pinned to 06200ef96b)