risingwavelabs/risingwave · critical

`checkpoint_read_max_in_flight_chunks` must be greater than

Error message

`checkpoint_read_max_in_flight_chunks` must be greater than 0

What it means

validate_config in src/meta/node/src/lib.rs:638 panics when `config.meta.checkpoint_read_max_in_flight_chunks` is 0. This is the concurrency limit for in-flight checkpoint read chunks; zero means no reads may ever be issued, so it is rejected at startup.

Source

Thrown at src/meta/node/src/lib.rs:638

        panic!("{}", error_msg);
    }

    if config.meta.parallelism_control_batch_size == 0 {
        let error_msg = "`parallelism_control_batch_size` must be greater than 0";
        tracing::error!(error_msg);
        panic!("{}", error_msg);
    }

    if config.meta.checkpoint_read_chunk_size == 0 {
        let error_msg = "`checkpoint_read_chunk_size` must be greater than 0";
        tracing::error!(error_msg);
        panic!("{}", error_msg);
    }

    if config.meta.checkpoint_read_max_in_flight_chunks == 0 {
        let error_msg = "`checkpoint_read_max_in_flight_chunks` must be greater than 0";
        tracing::error!(error_msg);
        panic!("{}", error_msg);
    }

    if config.meta.compaction_task_id_refill_capacity == 0 {
        let error_msg = "`compaction_task_id_refill_capacity` must be greater than 0";
        tracing::error!(error_msg);
        panic!("{}", error_msg);
    }

    if config.meta.iceberg_compaction_report_timeout_sec == 0 {
        let error_msg = "`iceberg_compaction_report_timeout_sec` must be greater than 0";
        tracing::error!(error_msg);
        panic!("{}", error_msg);
    }

    if config.meta.iceberg_compaction_config_refresh_interval_sec == 0 {
        let error_msg = "`iceberg_compaction_config_refresh_interval_sec` must be greater than 0";
        tracing::error!(error_msg);
        panic!("{}", error_msg);

View on GitHub (pinned to 6469eb736d)

Solutions

1. Set `meta.checkpoint_read_max_in_flight_chunks` to a positive integer (e.g. the default).
2. To reduce checkpoint read pressure, lower it to a small positive value like 1 instead of 0.
3. Remove the config line to restore the default.

Example fix

// before
[meta]
checkpoint_read_max_in_flight_chunks = 0

// after
[meta]
checkpoint_read_max_in_flight_chunks = 4

assert!(cfg.meta.checkpoint_read_max_in_flight_chunks > 0, "checkpoint_read_max_in_flight_chunks must be > 0");

When it happens

Trigger: Meta node startup with `meta.checkpoint_read_max_in_flight_chunks` set to 0 in the config.

Common situations: Attempts to throttle checkpoint reads to zero during maintenance, or wrong unit assumption (thinking it is a percentage).

Understand the failure class

Background: "Invalid value" and "allowed values are" config errors: what your library rejected and how to fix it — this error's family across 41 libraries.

Related errors

• `checkpoint_read_chunk_size` must be greater than 0
• `meta_leader_lease_secs` must be greater than 2
• `parallelism_control_batch_size` must be greater than 0
• `compaction_task_id_refill_capacity` must be greater than 0
• `iceberg_compaction_config_refresh_interval_sec` must be gre

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