Why the memory usage is so high?
RW_TOTAL_MEMORY_BYTES
/--total-memory-bytes
). This is why setting memory limits is required in Kubernetes/Docker deployments.During the instance running, RisingWave will keep memory usage below this limit. If you encounter unexpected issues like OOM (Out-of-memory), please refer to Troubleshoot out-of-memory for assistance.Why is the memory for compute nodes not fully utilized?
Details
--reserved-memory-bytes
and the environment variable RW_RESERVED_MEMORY_BYTES
to override the reserved memory configuration for compute nodes. Note that the memory reserved should be at least 512MB.Details
RW_RESERVED_MEMORY_BYTES=8589934592
or --reserved-memory-bytes=8589934592
when starting up the compute node. This will allocate 8GB as the reserved memory instead.Confused about the version difference of reserved memory setting?
Why does the `CREATE MATERIALIZED VIEW` statement take a long time to execute?
CREATE MATERIALIZED VIEW
statement can vary based on several factors. Here are two common reasons:SHOW JOBS;
in SQL to check the DDL progress. If you want the create statement to not wait for the process to finish and not block the session, you can execute SET BACKGROUND_DDL=true;
before running the CREATE MATERIALIZED VIEW
statement. See details in SET BACKGROUND_DDL. But please notice that the newly created MV is still invisible in the catalog until the end of backfill when BACKGROUND_DDL=true
.Progress
in the SHOW JOBS;
result stays at 0.0%, high latency could be the cause. See details in Troubleshoot high latencyWhat consists of the memory usage and disk usage?