Stability of standalone-mode

risingwavelabs / risingwave

SQL stream processing, analytics, and management. We decouple storage and compute to offer efficient joins, instant failover, dynamic scaling, speedy bootstrapping, and concurrent query serving.

https://www.risingwave.com/slack

Apache License 2.0

6.61k stars 543 forks source link

Stability of standalone-mode #12861

Open kwannoel opened 9 months ago

kwannoel commented 9 months ago

[ ] 1. Recovery test (regular ci testing in main-cron) #12802
[x] 2. e2e test (currently running daily in main-cron
[x] 3. Longevity test (requires cloud side support, we need https://linear.app/risingwave-labs/issue/CLOUD-1982/feature-replace-the-free-tier-deployment-with-standalone-mode first, so we can run standalone-mode in kube-bench.)
[x] 4. Performance test (requires cloud side support, as per 3.).
[ ] 5. Test docker-compose deployment of standalone mode. Should make sure failover is handled, i.e. if killed, the standalone node should still be able to recover.
[x] 6. #13235
[x] #13307

kwannoel commented 9 months ago

cc @neverchanje @arkbriar @huangjw806

huangjw806 commented 9 months ago

I think next I will integrate standalone-mode in kube-bench so we can test longevity and performance.

arkbriar commented 8 months ago

For the support of standalone risingwave on the operator side, you can take a look at https://github.com/risingwavelabs/risingwave-operator/pull/519.

kwannoel commented 6 months ago

Performance test on the cloud side is done. Any further updates @huangjw806 ? If not I think the high priority parts of this issue are complete.

huangjw806 commented 6 months ago

Performance test on the cloud side is done. Any further updates @huangjw806 ?

no updates.

github-actions[bot] commented 1 month ago

This issue has been open for 60 days with no activity. Could you please update the status? Feel free to continue discussion or close as not planned.