Elastic MapReduce upgraded its server and component service monitoring items on September 10, 2019. A new policy type "Elastic MapReduce" has been added, which covers hundreds of monitoring metrics. You can configure alarm policies under the Elastic MapReduce policy type in Cloud Monitor. The original policy type "EMR" was deprecated at 23:00 on March 30, 2021, and all the configured "EMR" alarm policies were invalidated. To add new alarm policies, configure under the "Elastic MapReduce" policy type.
Comparison of "EMR" and "Elastic MapReduce" policy types:
Policy Type
Metric Coverage
Support and Maintenance
EMR
Cluster alarming (12 metrics)
Node alarming (8 metrics)
It was deprecated at 23:00 on April 9, 2021 and no longer maintained.
Elastic MapReduce
Server monitoring
Service monitoring
Cluster monitoring
It was released on September 10, 2019 but is still maintained.
After the "EMR" policy type was deprecated, the system automatically migrated existing alarm policies under the "EMR" policy type to the "Elastic MapReduce" policy type. See further notifications for specific rules and verification methods.
Note:
A few users might need to migrate them manually.
Steps for manual migration are as follows:
1. Sort out exiting alarm metrics and policies.
Log in to the Cloud Monitor console, select Alarm Management > Alarm Configuration > Alarm Policy on the left sidebar, click Advanced Filter, select any sub-type of the "EMR" policy type in Policy Type, search for related alarm policies, and download them. Repeat this step to download the alarm policies under other sub-types of the "EMR" policy type.
2. Configure alarm policies.
Click Alarm Configuration in the cluster list to go to the Alarm Policy page, click Create, select Elastic MapReduce in Policy Type, and configure an alarm policy according to one of the policies sorted out and downloaded in step 1. Repeat this step to configure other alarm policies. For more information on the configuration method, see Alarm Configurations.
3. Verify the new alarm policies.
Verify that the "Elastic MapReduce" alarm policies are activated and can successfully trigger alarms. Set trigger thresholds in Metric Alarm, set recipient groups or recipients, and select receiving channels (email, SMS, or WeChat) for verification. Take memory zone percentage_SO as an example: when the statistical period is five minutes, and the percentage is greater than or equal to 1% and lasts for five minutes, an alarm will be triggered once every five minutes.
4. Delete original alarm policies.
After verifying the new alarm policies, delete the original alarm policies configured under the "EMR" policy type. Select any sub-type of the "EMR" policy type in Policy Type, search for related alarm policies, and delete them. Repeat this step to delete the alarm policies under other sub-types of the "EMR" policy type.
If you encounter any issues during the transfer, contact us for assistance.
Yes
No
Was this page helpful?