All Products
Search

This Product

    E-MapReduce:Lifecycle policy

    Document Center

    E-MapReduce:Lifecycle policy

    Last Updated:Feb 27, 2026

    E-MapReduce (EMR) follows a Runtime Lifecycle Policy (RLP) that governs how each release version moves from initial availability through end of support. This page defines each lifecycle phase, lists key dates for every EMR version, and explains what actions to take at each stage.

    For information about EMR version definitions, see Release versions.

    How the lifecycle works

    Every EMR release version progresses through three milestones:

    MilestoneWhat happensTypical timing
    General Availability (GA)The version is released for production use. Alibaba Cloud provides full technical support and an SLA guarantee.Day 0
    End of Marketing (EOM)New cluster purchases stop. Existing clusters continue to receive technical support and SLA coverage.~3 years after GA
    End of Service and Support (EOS)All support ends. No technical support, service, or security and stability SLA guarantees for remaining clusters.At least 1 year after EOM
    Phase durations are guidelines, not fixed intervals. The EMR team evaluates new version maturity, compatibility, and user demand before advancing any version. Dates may be postponed but are never moved earlier.

    What to do at each phase

    • GA -- No action required. Use the version in production with full support.

    • EOM -- Plan your migration. Upgrade existing clusters to a later version, or migrate workloads to EMR Serverless Spark or EMR Serverless StarRocks.

    • EOS -- Complete your migration before this date. After EOS, you assume all security and stability risks for any remaining clusters.

    Version lifecycle schedule

    Use the following tables to plan cluster upgrades. Versions are grouped by their current lifecycle status.

    Dates may be adjusted due to product planning, but they will not be moved earlier than listed.

    Versions past EOM

    These versions no longer accept new cluster purchases. Migrate existing clusters before EOS.

    VersionGAEOMEOS
    1.X.X series2015--2017September 30, 2024October 20, 2025
    2.X.X series2016--2018September 30, 2024October 20, 2025
    3.0.X--3.35.XBefore April 21, 2021September 30, 2024October 20, 2025
    4.0.X--4.9.XBefore April 21, 2021September 30, 2024October 20, 2025
    5.0.X--5.1.XBefore April 21, 2021September 30, 2024October 20, 2025
    3.36.XJuly 21, 2021September 30, 2024October 20, 2025
    5.2.XJuly 16, 2021September 30, 2024October 20, 2025
    3.37.XAugust 21, 2021September 30, 2024October 20, 2025
    5.3.XAugust 21, 2021September 30, 2024October 20, 2025
    3.38.XOctober 21, 2021October 20, 2024October 20, 2025
    5.4.XOctober 21, 2021October 20, 2024October 20, 2025

    Versions approaching EOM

    These versions will reach EOM on October 20, 2025. Plan your upgrade or migration.

    VersionGAEOMEOS
    3.39.XFebruary 15, 2022October 20, 2025October 20, 2026
    5.5.XFebruary 15, 2022October 20, 2025October 20, 2026
    4.10.XMarch 23, 2022October 20, 2025October 20, 2026
    3.40.XApril 21, 2022October 20, 2025October 20, 2026
    5.6.XApril 21, 2022October 20, 2025October 20, 2026
    3.41.XMay 15, 2022October 20, 2025October 20, 2026
    5.7.XMay 15, 2022October 20, 2025October 20, 2026
    3.42.XAugust 5, 2022October 20, 2025October 20, 2026
    5.8.XAugust 5, 2022October 20, 2025October 20, 2026

    Versions with scheduled EOM

    These versions will reach EOM on March 1, 2026.

    VersionGAEOMEOS
    3.43.XOctober 14, 2022March 1, 2026March 1, 2027
    5.9.XOctober 4, 2022March 1, 2026March 1, 2027
    3.44.XDecember 1, 2022March 1, 2026March 1, 2027
    5.10.XDecember 1, 2022March 1, 2026March 1, 2027
    3.45.XFebruary 28, 2023March 1, 2026March 1, 2027
    5.11.XFebruary 28, 2023March 1, 2026March 1, 2027

    Versions with no scheduled EOM

    These versions are under active support. EOM and EOS dates will be announced at least three months in advance.

    VersionGAEOMEOS
    3.46.XJune 1, 2023To be determinedTo be determined
    5.12.XJune 1, 2023To be determinedTo be determined
    3.47.XAugust 3, 2023To be determinedTo be determined
    5.13.XAugust 3, 2023To be determinedTo be determined
    3.48.XAugust 17, 2023To be determinedTo be determined
    5.14.XAugust 17, 2023To be determinedTo be determined
    3.49.XOctober 27, 2023To be determinedTo be determined
    5.15.XOctober 27, 2023To be determinedTo be determined
    3.50.XFebruary 19, 2024To be determinedTo be determined
    5.16.XFebruary 19, 2024To be determinedTo be determined
    3.51.XApril 23, 2024To be determinedTo be determined
    5.17.XApril 23, 2024To be determinedTo be determined
    3.52.XDecember 4, 2024To be determinedTo be determined
    5.18.XDecember 4, 2024To be determinedTo be determined

    Notifications

    Alibaba Cloud notifies you at least three months before each lifecycle milestone through the following channels:

    • Announcements

    • Internal messages

    • Emails

    • Text messages

    Before a version reaches EOM or EOS, the EMR team helps evaluate job-running risks and provides migration guidance. To share feedback or ask questions about lifecycle changes, contact your sales representative or reach out through the DingTalk service group.

    Update history

    DateDescription
    June 11, 2025Revised version-to-lifecycle mappings. Added EOS announcements for certain versions. Updated EOM announcements.
    March 31, 2025Added EOM information for EMR V3.39.X, V5.5.X, and later versions.
    November 8, 2024Added information about purchases and renewals during the EOM phase.
    October 17, 2023Initial release.