This topic describes the optimization of the Expiration Time parameter for E-MapReduce (EMR) clusters of old types, such as Hadoop, ZooKeeper, Data Science, Druid, Shuffle Service, Presto, EMR Studio, ClickHouse, Flink, and Kafka. The optimization improves the timeliness of the EMR service. The optimization helps you control the lifecycle of EMR clusters and ensures the continuity of O&M on EMR clusters when the clusters expire.
Effective scope
The optimization applies to subscription clusters of old types, such as ZooKeeper, Data Science, Druid, Shuffle Service, Presto, EMR Studio, ClickHouse, Flink, and Kafka.
Effective date
July 25, 2024
Optimization effects
The Expiration Time parameter specifies the earliest expiration time of an EMR instance in your cluster.
Impacts
If your cluster contains expired EMR instances, you may fail to perform specific O&M operations on the cluster. This affects the flexibility in daily cluster management. For more information, see Subscription.
The submitted tasks and executed processes are not affected by the limit on the O&M feature.
Solution
Go to the Renew page of the desired cluster and renew the expired EMR instances. After the renewal is complete, you can continuously use all features of the EMR service as expected.