Skip to main content

Set up a local RisingWave cluster with Docker Compose

This article will help you use the pre-defined Docker Compose configuration file to set up a full-featured multi-node RisingWave cluster.


If you intend to deploy RisingWave in production environments, please use the Kubernetes Operator for RisingWave. This is because it has better support for resource management, and we do comprehensive tests for it. To learn about how to deploy RisingWave using the Kubernetes Operator, see Kubernetes.

The cluster is composed of multiple RisingWave components, including:

  • A frontend node
  • A compute node
  • A meta node
  • A compactor node
  • A connector node

RisingWave also incorporates these third-party components:

  • Grafana
  • Etcd
  • MinIO
  • Prometheus

Download the source file and start a cluster

As prerequisites, you need to install Docker Desktop in your environment. Ensure that it is running before launching the cluster.

Then, clone the risingwave repository.

git clone

Now run the following commands to navigate to the docker directory and start the cluster from the pre-defined docker-compose file.

cd docker
docker compose up -d

Connect to RisingWave

After RisingWave is up and running, you need to connect to it via the Postgres interactive terminal psql so that you can issue queries to RisingWave and see the query results.

psql -h localhost -p 4566 -d dev -U root

You can now connect a streaming source to RisingWave and issue SQL queries to manage your data.

Manage your RisingWave cluster

When the cluster is running, you can monitor the status of RisingWave and the additional components and make adjustments when necessary.

RisingWave Dashboard

Access the RisingWave Dashboard at RisingWave Dashboard displays an overview of the cluster, as well as sources, sinks, tables, materialized views, and indexes available on the cluster.


Access Grafana at, and search for risingwave_dashboard. In this dashboard, you can view the internal metrics such as node count, memory consumption, thoroughputs, and latencies. You can use these metrics to troubleshoot and optimize the cluster performance.


Access the MinIO instance at Use the following credentials to log in.

  • User name: hummockadmin
  • Password: hummockadmin


Access Prometheus at No credentials are needed. You can use Prometheus for real-time alerting.

Help us make this doc better!