Cannot downgrade SR version from 3.3.4 to 3.1.10, error `Cluster backendIdList must be 0` occurred

StarRocks / starrocks

The world's fastest open query engine for sub-second analytics both on and off the data lakehouse. With the flexibility to support nearly any scenario, StarRocks provides best-in-class performance for multi-dimensional analytics, real-time analytics, and ad-hoc queries. A Linux Foundation project.

https://starrocks.io

Apache License 2.0

9.03k stars 1.82k forks source link

Cannot downgrade SR version from 3.3.4 to 3.1.10, error `Cluster backendIdList must be 0` occurred #53092

Open Xiangakun opened 21 hours ago

Xiangakun commented 21 hours ago

Steps to reproduce the behavior (Required)

Start SR cluster with version 3.1.10 & add some tables for test
Upgrade version 3.1.10 to version 3.3.4
Downgrade version back to 3.1.10

Expected behavior (Required)

Downgrade version back to 3.1.10 successfully

Real behavior (Required)

error java.lang.IllegalStateException: Cluster backendIdList must be 0 occurred

StarRocks version (Required)

You can get the StarRocks version by executing SQL select current_version()

3.3.4 -> 3.1.10

Xiangakun commented 21 hours ago

I checked the code, it should be caused by the default_cluster is removed from 3.3.4, and it's still in use in version 3.1.10, and it's not a must for version 3.1.10 either. I think we can add a config for user to avoid to create the default_cluster in 3.1.10 under such circumstance.