All Products
Search

This Product

    E-MapReduce:Version lifecycle policy

    Document Center

    E-MapReduce:Version lifecycle policy

    Last Updated:Mar 25, 2026

    EMR Serverless StarRocks follows a Runtime Lifecycle Policy (RLP) that defines the support period for each distribution version — from General Availability (GA) through End of Service and Support (EOS).

    Lifecycle phases

    Each distribution version passes through two milestones:

    image

    Milestone

    Definition

    Time point

    Description

    General Availability (GA)

    Official release

    Month T

    The version is officially released and ready for production use.

    End of Service and Support (EOS)

    Service and support termination

    Month T + 2 years

    No new versions, including patch versions, are released. User Q&A, issue resolution, and Service Level Agreement (SLA) compensation are suspended.

    Important

    If a version has a critical bug affecting data accuracy, security, or stability, StarRocks reserves the right to immediately stop new purchases of that version. Existing customers will be notified promptly and must complete the upgrade within the timeframe specified in the notice. Business impact resulting from a failure to upgrade on time is not covered by the SLA.

    Version lifecycle dates

    Lifecycle management is based on major versions. All minor versions inherit the EOS date of their major version.

    Note

    The EOS date for some versions may be extended. See the description for each version below.

    Major version

    GA

    EOS

    Description

    2.5

    Jan. 2024

    Jan. 2027

    • Because version 2.5 is the Long-Term Support (LTS) version of the StarRocks open-source 2.X series, its EOS date is extended to January 2027.

    • This version does not support rolling upgrades to 3.x versions. To upgrade to a 3.x series version, you must migrate the instance.

    3.1

    Jan. 2024

    Jan. 2026

    New purchases are discontinued. Use version 3.3 instead.

    3.2

    Mar. 2024

    Dec. 2026

    This is a historical LTS version with integrated storage and computing. Its EOS date is extended to December 2026.

    3.3

    Dec. 2024

    Dec. 2026

    -

    Support and notifications

    To help you plan upgrades and migrations, Alibaba Cloud provides the following support:

    • Transparent lifecycle plan: A detailed lifecycle plan is published for each StarRocks version and communicated through official channels such as product documentation and announcements.

    • Advance notice for key milestones: For instances approaching EOS, StarRocks notifies customers at least three months in advance and provides technical support to help upgrade to the latest stable version before the EOS date. Notifications are sent through:

      • Company announcements and product documentation

      • Internal messages, emails, and SMS

    • Technical support and assistance: When a version is approaching end of service, StarRocks provides professional technical support to help you assess job execution risks and explore viable solutions for a smooth business transition.

    Version overview

    EMR Serverless StarRocks uses a two-tier versioning system — major versions and patch versions. On the Instance Details page for your instance in the StarRocks console, you can view the current version and available upgrade versions.

    Version types

    Version type

    Example

    Description

    Major version

    2.5, 3.2, 3.3

    Synchronized with the StarRocks community main version. Represents a major evolution of core features and architecture.

    Patch version

    3.3.3-1.1.0-1.7.12

    • 3.3.3: The StarRocks kernel minor version, consistent with the community version. The first two digits (3.3) correspond to the major version; the last digit (3) is the third minor version within major version 3.3.

    • 1.1.0: The version of the EMR Serverless StarRocks enterprise-grade kernel (Stella) — the first major version, first minor version.

    • 1.7.12: The management platform version, covering console, monitoring, and O&M features — the seventh major version, twelfth minor version.

    Version compatibility

    Minor version compatibility

    All minor versions within the same major version are compatible. Compatibility covers:

    • SQL syntax

    • Client interfaces — Java Database Connectivity (JDBC) and Open Database Connectivity (ODBC)

    • Table schemas and data formats

    Compatibility is not guaranteed for program logic behavior, such as changes in specific query performance.

    Upgrade to the latest minor version of your current major version for the best stability and feature experience.

    Major version compatibility

    Full compatibility between major versions is not guaranteed. Although SQL syntax, interfaces, and behavior are kept as consistent as possible, the following changes may occur when following community version evolution:

    • SQL syntax adjustments or deprecations

    • Interface changes or parameter adjustments

    • Changes in the default values of configuration items

    • Performance fluctuations caused by query execution plan optimizations

    Before upgrading across major versions:

    1. Review the version release notes to understand new features and potential impacts.

    2. Verify business compatibility in a test environment.

    3. Avoid major version upgrades during peak business hours.

    Release notes and resources

    What's next

    For questions about version lifecycle management, contact the technical support team.