Stability of standalone-mode

[kwannoel]

• 1. Recovery test (regular ci testing in main-cron) Test recovery of single node mode / sql backend recovery #12802
• 2. e2e test (currently running daily in main-cron
• 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.)
• 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.
• 6. Use standalone as default docker compose mode #13235
• Use standalone-mode for all integration tests. #13307

[kwannoel]

cc @neverchanje @arkbriar @huangjw806

[huangjw806]

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

[arkbriar]

For the support of standalone risingwave on the operator side, you can take a look at risingwavelabs/risingwave-operator#519.

[kwannoel]

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]

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

no updates.

[github-actions]

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.