risingwavelabs/risingwave · error · SchedulerError

BatchError

Error message

BatchError

What it means

SchedulerError::BatchError is a transparent wrapper (via #[from]) over risingwave_batch::error::BatchError, so the displayed message is the underlying batch engine error. It surfaces when batch executor construction or execution inside the compute engine fails and the error propagates up to the frontend scheduler.

Source

Thrown at src/frontend/src/scheduler/error.rs:51

        RpcError,
    ),

    #[error("{0}")]
    TaskExecutionError(String),

    #[error("Task got killed because compute node running out of memory")]
    TaskRunningOutOfMemory,

    /// Used when receive cancel request for some reason, such as user cancel or timeout.
    #[error("Query cancelled: {0}")]
    QueryCancelled(String),

    #[error(
        "Reject query: the {0} query number reaches the limit: {1}. Use `SHOW PROCESSLIST` to check for hanging queries and cancel them if needed."
    )]
    QueryReachLimit(QueryMode, u64),

    #[error(transparent)]
    BatchError(
        #[from]
        #[backtrace]
        BatchError,
    ),

    #[error(transparent)]
    Connector(
        #[from]
        #[backtrace]
        ConnectorError,
    ),

    #[error(transparent)]
    Internal(
        #[from]
        #[backtrace]
        anyhow::Error,

View on GitHub (pinned to 6469eb736d)

Solutions

1. Read the transparent BatchError chain and compute node logs for the root cause; the scheduler error itself is just a pass-through.
2. Retry the query if it followed a node restart or DDL race.
3. Ensure frontend and compute node versions match (no version skew in a rolling upgrade).
4. If reproducible with a specific query, minimize it and file a bug with the full error chain.

// unwrap the transparent cause before reporting
catch (e) { const cause = e.cause ?? e; log(cause); if (isTransient(cause)) retry(); else throw cause; }

When it happens

Trigger: Building or executing a batch plan fails in the batch engine — e.g. an executor error during a distributed stage, invalid plan fragment, serialization of exec fields, or an internal batch assertion failure.

Common situations: Internal bugs in batch executors; incompatible plan fragments after version skew between frontend and compute nodes; task environment setup failures (e.g. missing tables after DDL races).

Understand the failure class

Background: "query failed", "%w: SQL error" — wrapped database query errors in Go libraries explained — this error's family across 3 libraries.

Related errors

• {0}
• Task got killed because compute node running out of memory
• Pin snapshot error: {0} fails to get epoch {1}
• RpcError
• Query cancelled: {0}

AI-assisted analysis of risingwavelabs/risingwave@6469eb736d (2026-09-11). Data as JSON: /api/errors/6e114e2e257d4da8. Report an issue: GitHub.