Skip to main content
Serverless backfill is available starting from v2.8.0 and is disabled by default.

​
Overview

When you create a materialized view (MV) on existing data, RisingWave must first process all historical records, a phase called backfill. By default, this runs on the same compute nodes as your regular streaming workloads, which can cause resource contention and increased latency for existing pipelines. Serverless backfill offloads the backfill phase to a dedicated controller that manages execution independently from your main streaming graph. This decoupling helps large backfills complete while reducing their impact on the performance of existing streaming jobs. Serverless backfilling is supported only in RisingWave Cloud. Enable it under Resources -> Backfillings in the Cloud console first. See Serverless backfilling for portal setup, SKU, and replicas.

​
How it works

When serverless backfill is enabled for a CREATE MATERIALIZED VIEW statement:
  1. The frontend generates a backfill plan and hands it to the serverless backfill controller.
  2. The controller schedules and drives the backfill execution separately from the main streaming graph.
  3. Once all backfill fragments report completion, the MV transitions to the standard incremental streaming phase.
  4. If the cluster restarts during backfill, the controller resumes from the last completed checkpoint rather than starting over.
  • Serverless backfilling is not supported for databases in non-default resource groups.

​
Configuration

​
Session variable

Enable serverless backfill for subsequent CREATE MATERIALIZED VIEW statements in the current session: 
SET enable_serverless_backfill = true;
The default is false. This setting only affects new DDL operations issued after the SET command; it does not change the behavior of already-running jobs.

​
Per-statement WITH clause

You can also enable serverless backfill for a single CREATE MATERIALIZED VIEW statement using the cloud.serverless_backfill_enabled option in the WITH clause: 
CREATE MATERIALIZED VIEW my_mv
WITH (cloud.serverless_backfill_enabled = true)
AS SELECT ...;

​
Example

The following example creates a large materialized view with serverless backfill enabled to reduce the impact of the backfill on existing streaming workloads:
Example: serverless backfill
-- Enable serverless backfill for this session
SET enable_serverless_backfill = true;

-- Optionally run in the background to avoid blocking the client
SET BACKGROUND_DDL = true;

CREATE MATERIALIZED VIEW orders_summary AS
SELECT customer_id, COUNT(*) AS order_count, SUM(amount) AS total_amount
FROM orders
GROUP BY customer_id;
If you want to enable it only for one statement, use: 
CREATE MATERIALIZED VIEW orders_summary
WITH (cloud.serverless_backfill_enabled = true)
AS
SELECT customer_id, COUNT(*) AS order_count, SUM(amount) AS total_amount
FROM orders
GROUP BY customer_id;
After issuing the statement, you can monitor progress with:
Monitor progress
SELECT * FROM rw_catalog.rw_ddl_progress;

​
Monitoring

Use the following system catalog and metrics to track serverless backfill jobs:
MethodDescription
SHOW JOBSLists all background DDL jobs and their current status.
SELECT * FROM rw_catalog.rw_ddl_progressShows per-fragment backfill progress as a percentage.
Grafana / metrics endpointLook for stream_backfill_* metrics on compute nodes to observe throughput and lag.

​
Limitations

  • Serverless backfilling is supported only in RisingWave Cloud, and you must enable it under Resources -> Backfillings before requesting it in SQL.
  • Serverless backfilling is not supported for databases in non-default resource groups.
  • Rate-limiting via backfill_rate_limit still applies to serverless backfill jobs. See View and configure runtime parameters.