troubleshooting

Could switching to distributed deployment on k8s help with storage issues in RisingWave?

I'm facing storage issues in RisingWave despite the statelessness of the queries. The barrier latency p99 is high with spikes, and I see errors related to compaction and vacuum in the logs. Would switching to a distributed deployment on Kubernetes help with these storage issues?

Kr

Krzysztof Sota

Asked on Apr 25, 2024

  • Switching to a distributed deployment on Kubernetes can potentially help with storage issues in RisingWave.
  • Distributed deployments can provide better scalability and resource management, which may alleviate storage-related problems.
  • Kubernetes offers features like dynamic storage provisioning and scaling, which can be beneficial for handling large volumes of data.
  • It's important to consider the architecture and design of the deployment to ensure efficient utilization of resources and optimal performance.

Example:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: risingwave-deployment
spec:
  replicas: 3
  selector:
    matchLabels:
      app: risingwave
  template:
    metadata:
      labels:
        app: risingwave
    spec:
      containers:
      - name: risingwave
        image: your-risingwave-image:latest
        ports:
        - containerPort: 8080
      ```
Apr 25, 2024Edited by