@Rocky Can we upgrade from 3.5.x to 4.1.0? or need to upgrade to 4.0.x first

For upgrading from StarRocks 3.5.x to 4.1.0, it is strongly recommended to follow a consecutive upgrade path through the 4.0.x minor version. Recommended Upgrade Path Based on StarRocks' upgrade documentation, while the system technically allows crossing minor versions from v2.0 onwards, the best practice for metadata safety and stability is: v3.5.x $\rightarrow$ v4.0.x $\rightarrow$ v4.1.0 Key Considerations 1. Consecutive Minor Versions: StarRocks documentation recommends upgrading consecutively from one minor version to another (e.g., 3.5 to 4.0, then 4.0 to 4.1). This ensures that metadata migrations are handled step-by-step and reduces the risk of incompatibility. 2. Metadata Image: Between each minor version jump (e.g., after reaching a stable 4.0.x), you should run

ALTER SYSTEM CREATE IMAGE

and wait for the image to synchronize to all Follower FEs before proceeding to the next minor version (4.1.0). This prevents metadata upgrade failures on Follower nodes. 3. JDK Requirement: Since you are already on 3.5.x, you should already be using JDK 17, which continues to be the requirement for the 4.x series. 4. Downgrade Note: If you upgrade to v4.0 and encounter issues, do not downgrade directly to v3.5.0 or v3.5.1, as this can cause FE crashes. You must be on v3.5.2 or later for a safe downgrade path from 4.0. 5. Rolling Upgrade Order: Always follow the standard rolling upgrade sequence: * Upgrade BEs (and CNs) one by one. * Upgrade Follower FEs one by one. * Finally, upgrade the Leader FE. Summary To ensure the safest transition, upgrade to v4.0.x first, verify the cluster health and metadata image, and then proceed to v4.1.0. Avoid jumping directly from 3.5.x to 4.1.0 to minimize risks associated with skipping minor version metadata changes. References • release_notes/release-4.0.md