This topic describes bug fixes for various versions of StarRocks, including their problem descriptions and impact levels. Use the error messages and problem descriptions to identify issues that may affect your business, and take preventive measures.
Background information
Bug and fix descriptions
Bug persistence: A bug found in a specific version is generally also present in all earlier versions.
For example, a bug in version 3.3.8 usually exists in earlier versions, such as 3.3.2 and 3.2.0. Any exceptions are clearly noted.
Fix inclusion: A bug fixed in a specific version remains fixed in all subsequent versions.
For example, a bug fixed in version 3.3.8 is also fixed in that version and all subsequent versions, such as 3.3.13.
Bug level descriptions
P0: Upgrade immediately. If this bug is triggered, it affects online services and can impact query accuracy and write success rates.
P1: An upgrade is recommended to prevent these issues.
P2: An upgrade is optional. These issues occur occasionally and can usually be fixed by rewriting a method or restarting the service.
August 2025
Bug description | Bug level | Cause | Instance type | Affected versions | Recommended action |
FE node fails to start | P0 | The FE replay thread incorrectly deletes StarOS metadata, which can prevent the FE node from starting. | Storage-compute separation | 3.3.0 to 3.3.8 | Upgrade to the latest 3.3.x version with compute-storage separation. The current latest version is 3.3.13-1.1.1. |
BE node goes down | P0 | Batch Publish can cause version discontinuities, which may cause a BE node to go down. | Storage-compute separation |
| Upgrade to the latest 3.3.x version for shared-data clusters. The current latest version is 3.3.13-1.1.1. |