serving node, streaming node, meta node, and compactor node are all embedded in this process.
RisingWave by default uses object storage to persist data. In the standalone mode, we use the embedded LocalFs Object Store, eliminating the need for an external service like minio or s3; for meta store, we will use the embedded SQLite database, eliminating the need for an external service like etcd.
By default, the RisingWave standalone mode will store its data in ~/.risingwave, which includes both Metadata and State Data.
For a batteries-included setup, with monitoring tools and external services like kafka fully included, you can use Docker Compose instead. If you would like to set up these external services manually, you may check out RisingWave’s Docker Compose, and run these services using the same configurations.
Configure RisingWave standalone mode
The instance of RisingWave standalone mode can run without any configuration. However, there are some options available to customize the instance. The main options which new users may require would be the state store directory (--state-store-directory) and in-memory mode (--in-memory).
--state-store-directory specifies the new directory where the cluster’s Metadata and State Data will reside. The default is to store it in the ~/.risingwave folder.
--in-memory will run an in-memory instance of RisingWave, both Metadata and State Data will not be persisted.
Monitor RisingWave standalone mode with Grafana and Prometheus
To monitor your standalone cluster, you may wish to integrate metrics monitoring with Grafana and Prometheus. First install Grafana and Prometheus. Next, clone the RisingWave repository, it contains various configuration files. Start the RisingWave standalone cluster. Make sure you’re in theRisingWave directory.
Start your prometheus instance:
grafana/risingwave-dev-dashboard.json, grafana/risingwave-user-dashboard.json.
With that you can now monitor your standalone cluster with Grafana and Prometheus.