risingwavelabs/risingwave · warning · MetaError

Cancelled: {0}

Error message

Cancelled: {0}

What it means

The requested operation was cancelled before completion. Carries a human-readable reason string. Typically surfaces when a client disconnects, a task is aborted, or an explicit cancellation was issued.

Source

Thrown at src/meta/src/error.rs:97

    #[error("table_fragment does not exist: id={0}")]
    FragmentNotFound(FragmentId),

    #[error("{0} named {1} already exists{under_creation}", under_creation = (.2).map(|_| " and is still being created").unwrap_or(""))]
    Duplicated(
        &'static str,
        String,
        // if under creation, take streaming job id, otherwise None
        Option<JobId>,
    ),

    #[error("Service unavailable: {0}")]
    Unavailable(#[message] String),

    #[error("Election failed: {0}")]
    Election(#[source] BoxedError),

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

    #[error("System parameters error: {0}")]
    SystemParams(String),

    #[error("Session parameters error: {0}")]
    SessionConfig(
        #[from]
        #[backtrace]
        SessionConfigError,
    ),

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

View on GitHub (pinned to 6469eb736d)

Solutions

1. Check the message for the cancellation reason.
2. If the user cancelled intentionally, no action needed; resubmit if the work is still wanted.
3. If a DDL job was cancelled, check for leftover partial state and clean up or recreate.
4. Retry the operation after ensuring the client stays connected for long-running requests.

match meta_result {
    Err(MetaError::Cancelled(reason)) => { /* inspect reason; resubmit if work is still wanted */ }
    other => other?,
}

When it happens

Trigger: Client drops the RPC connection mid-request, a streaming DDL job is cancelled via `CANCEL JOBS`, internal task aborts due to shutdown or timeouts.

Common situations: User cancels a long-running materialized view creation, psql/CLI closed while a query ran, meta node graceful shutdown aborting in-flight work.

Related errors

• anyhow!(message.to_owned())
• {message}: in worker node {}, {};
• Invalid worker: {0}, {1}
• Service unavailable: {0}
• Receive shutdown msg: {msg:?}

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