Analyze Amazon EMR on Amazon EC2 cluster utilization with Amazon Athena and Amazon QuickSight

Gaining granular visibility into application-level prices on Amazon EMR on Amazon Elastic Compute Cloud (Amazon EC2) clusters presents a chance for patrons on the lookout for methods to additional optimize useful resource utilization and implement honest value allocation and chargeback fashions. By breaking down the utilization of particular person purposes operating in your EMR cluster, you’ll be able to unlock a number of advantages:

• Knowledgeable workload administration – Utility-level value insights empower organizations to prioritize and schedule workloads successfully. Useful resource allocation choices might be made with a greater understanding of value implications, doubtlessly enhancing general cluster efficiency and cost-efficiency.
• Price optimization – With granular value attribution, organizations can determine cost-saving alternatives for particular person purposes. They will right-size underutilized sources or prioritize optimization efforts for purposes which can be driving excessive utilization and prices.
• Clear billing – In multi-tenant environments, organizations can implement honest and clear value allocation fashions primarily based on particular person utility useful resource consumption and related prices. This fosters accountability and allows correct chargebacks to tenants.

On this publish, we information you thru deploying a complete answer in your Amazon Net Companies (AWS) setting to investigate Amazon EMR on EC2 cluster utilization. Through the use of this answer, you’ll acquire a deep understanding of useful resource consumption and related prices of particular person purposes operating in your EMR cluster. This can aid you optimize prices, implement honest billing practices, and make knowledgeable choices about workload administration, finally enhancing the general effectivity and cost-effectiveness of your Amazon EMR setting. This answer has been solely examined on Spark workloads operating on EMR on EC2 that makes use of YARN as its useful resource supervisor. It hasn’t been examined on workloads from different frameworks that run on YARN, resembling HIVE or TEZ.

Resolution overview

The answer works by operating a Python script on the EMR cluster’s major node to gather metrics from the YARN useful resource supervisor and correlate them with value utilization particulars from the AWS Price and Utilization Studies (AWS CUR). The script activated by a cronjob makes HTTP requests to the YARN useful resource supervisor to gather two kinds of metrics from paths /ws/v1/cluster/metrics for cluster metrics and /ws/v1/cluster/apps for utility metrics. The cluster metrics include utilization data of cluster sources, and the appliance metrics include utilization data of an utility or job. These metrics are saved in an Amazon Easy Storage Service (Amazon S3) bucket.

There are two YARN metrics that seize the useful resource utilization data of an utility or job.

• memorySeconds – That is the reminiscence (in MB) allotted to an utility instances the variety of seconds the appliance ran
• vcoreSeconds – That is the variety of YARN vcores allotted to an utility instances the variety of seconds utility ran

The answer makes use of memorySeconds to derive the price of operating the appliance or job. It may be modified to make use of vcoreSeconds as an alternative if obligatory.

The metadata of the YARN metrics collected in Amazon S3 is created, saved, and represented as database and tables in AWS Glue Knowledge Catalog, which is in flip out there to Amazon Athena for additional processing. Now you can write SQL queries in Athena to correlate the YARN metrics with the price utilization data from AWS CUR to derive the detailed value breakdown of your EMR cluster by infrastructure and utility. This answer creates two corresponding Athena views of the respective value breakdown that can turn out to be the information supply to Amazon QuickSight for visualization.

The next diagram exhibits the answer structure.

Stipulations

To carry out the answer, you want the next stipulations:

1. Verify {that a} CUR is created in your AWS account. It wants an S3 bucket to retailer the report recordsdata. Comply with the steps described in Creating Price and Utilization Studies to create the CUR on the AWS Administration Console. When creating the report, be certain that the next settings are enabled:

• • Embody useful resource IDs
  • Time granularity is about to hourly
  • Report information integration to Athena

It will possibly take as much as 24 hours for AWS to start out delivering stories to your S3 bucket. Thereafter, your CUR will get up to date a minimum of one time a day.

2. The answer wants Athena to run queries towards the information from the CUR utilizing normal SQL. To automate and streamline the combination of Athena with CUR, AWS supplies an AWS CloudFormation template, crawler-cfn.yml, which is routinely generated in the identical S3 bucket throughout CUR creation. Comply with the directions in Organising Athena utilizing AWS CloudFormation templates to combine Athena with the CUR. This template will create an AWS Glue database that references to the CUR, an AWS Lambda occasion and an AWS Glue crawler that will get invoked by S3 occasion notification to replace the AWS Glue database every time the CUR will get up to date.
3. Ensure that to activate the AWS generated value allocation tag, aws:elasticmapreduce:job-flow-id. This permits the sphere, resource_tags_aws_elasticmapreduce_job_flow_id, within the CUR to be populated with the EMR cluster ID and is utilized by the SQL queries within the answer. To activate the price allocation tag from the administration console, comply with these steps:
   • Check in to the payer account’s AWS Administration Console and open the AWS Billing and Price Administration console
   • Within the navigation pane, select Price Allocation Tags
   • Underneath AWS generated value allocation tags, select the aws:elasticmapreduce:job-flow-id tag
   • Select Activate. It will possibly take as much as 24 hours for tags to activate.

The next screenshot exhibits an instance of the aws:elasticmapreduce:job-flow-id tag being activated.

Now you can check out this answer on an EMR cluster in a lab setting. If you happen to’re not already aware of EMR, comply with the detailed directions offered in Tutorial: Getting began with Amazon EMR to launch a brand new EMR cluster and run a pattern Spark job.

Deploying the answer

To deploy the answer, comply with the steps within the subsequent sections.

Putting in scripts to the EMR cluster

Obtain two scripts from the GitHub repository and save them into an S3 bucket:

• emr_usage_report.py – Python script that makes the HTTP requests to YARN Useful resource Supervisor
• emr_install_report.sh  – Bash script that creates a cronjob to run the python script each minute

To put in the scripts, add a step to the EMR cluster by means of the console or AWS Command Line Interface (AWS CLI) utilizing aws emr add-step command.

Exchange:

• REGION with the AWS Areas the place the cluster is operating (for instance, Europe (Eire) eu-west-1)
• MY-BUCKET with the title of the bucket the place the script is saved (for instance, my.artifact.bucket)
• MY_REPORT_BUCKET with the bucket title the place you wish to accumulate YARN metrics (for instance, my.report.bucket)

aws emr add-steps 
--cluster-id j-XXXXXXXXXXXXX 
--steps Kind=CUSTOM_JAR,Title="Set up YARN reporter",Jar=s3://REGION.elasticmapreduce/libs/script-runner/script-runner.jar,Args=[s3:///emr-install_reporter.sh,s3:///emr_usage_reporter.py,MY_REPORT_BUCKET]

Now you can run some Spark jobs in your EMR cluster to start out producing utility utilization metrics.

Launching the CloudFormation stack

When the stipulations are met and you’ve got the scripts deployed in order that your EMR clusters are sending YARN metrics to an S3 bucket, the remainder of the answer might be deployed utilizing CloudFormation.

Earlier than launching the stack, add a duplicate of this QuickSight definition file into an S3 bucket required by the CloudFormation template to construct the preliminary evaluation in QuickSight. When prepared, proceed to launch your stack to provision the remaining sources of the answer.

1. Select
   

This routinely launches AWS CloudFormation in your AWS account with a template. It prompts you to check in as wanted and ensure you create the stack in your supposed Area.

The CloudFormation stack requires a couple of parameters, as proven within the following screenshot.

The next desk describes the parameters.

2. Enter the parameter values from the previous desk.
3. Select Subsequent.
4. On the following display screen, enter any obligatory tags, an AWS Identification and Entry Administration (IAM) function, stack failure, or superior choices if obligatory. In any other case, you’ll be able to go away them as default.
5. Select Subsequent.
6. Overview the main points on the ultimate display screen and choose the examine bins confirming AWS CloudFormation would possibly create IAM sources with customized names or require CAPABILITY_AUTO_EXPAND.
   
7. Select Create.

The stack will take a few minutes to create the remaining sources for the answer. After the CloudFormation stack is created, on the Outputs tab, you will discover the main points of the sources created.

Reviewing the correlation outcomes

The CloudFormation template creates two Athena views containing the correlated value breakdown particulars of the YARN cluster and utility metrics with the CUR. The CUR aggregates value hourly and due to this fact correlation to derive the price of operating an utility is prorated primarily based on the hourly operating value of the EMR cluster.

The next screenshot exhibits the Athena view for the correlated value breakdown particulars of YARN cluster metrics.

The next desk describes the fields within the Athena view for YARN cluster metrics.

The next screenshot exhibits the Athena view for the correlated value breakdown particulars of YARN utility metrics.

The next desk describes the fields within the Athena view for YARN utility metrics.

Constructing your individual visualization

In QuickSight, the CloudFormation template creates two datasets that reference Athena views as information sources and a pattern evaluation. The pattern evaluation has two sheets, EMR Infra Spend and EMR App Spend. They’ve a prepopulated bar chart and pivot tables to reveal how you should use the datasets to construct your individual visualization to current the price breakdown particulars of your EMR clusters.

EMR Infra Spend sheet references to the YARN cluster metrics dataset. There’s a filter for date vary choice and a filter for cluster ID choice. The pattern bar chart exhibits the consolidated value breakdown of the sources for every cluster through the interval. The pivot desk breaks them down additional to indicate their day by day expenditure.

The next screenshot exhibits the EMR Infra Spend sheet from pattern evaluation created by the CloudFormation template.

EMR App Spend sheet references to the YARN utility metrics. There’s a filter for date vary choice and a filter for cluster ID choice. The pivot desk on this sheet exhibits how you should use the fields within the dataset to current the price breakdown particulars of the cluster by customers to watch the purposes that had been run, whether or not they had been accomplished efficiently or not, the time and length of every run, and the derived value of the run.

The next screenshot exhibits the EMR App Spend sheet from pattern evaluation created by the CloudFormation template.

Cleanup

If you happen to not want the sources you created throughout this walkthrough, delete them to forestall incurring extra prices. To wash up your sources, full the next steps:

1. On the CloudFormation console, delete the stack that you simply created utilizing the template
2. Terminate the EMR cluster
3. Empty or delete the S3 bucket used for YARN metrics

Conclusion

On this publish, we mentioned learn how to implement a complete cluster utilization reporting answer that gives granular visibility into the useful resource consumption and related prices of particular person purposes operating in your Amazon EMR on EC2 cluster. Through the use of the ability of Athena and QuickSight to correlate YARN metrics with value utilization particulars out of your Price and Utilization Report, this answer empowers organizations to make knowledgeable choices. With these insights, you’ll be able to optimize useful resource allocation, implement honest and clear billing fashions primarily based on precise utility utilization, and finally obtain better cost-efficiency in your EMR environments. This answer will aid you unlock the complete potential of your EMR cluster, driving steady enchancment in your information processing and analytics workflows whereas maximizing return on funding.

In regards to the authors

Boon Lee Eu is a Senior Technical Account Supervisor at Amazon Net Companies (AWS). He works carefully and proactively with Enterprise Help prospects to offer advocacy and strategic technical steerage to assist plan and obtain operational excellence in AWS setting primarily based on finest practices. Based mostly in Singapore, Boon Lee has over 20 years of expertise in IT & Telecom industries.

Kyara Labrador is a Sr. Analytics Specialist Options Architect at Amazon Net Companies (AWS) Philippines, specializing in massive information and analytics. She helps prospects in designing and implementing scalable, safe, and cost-effective information options, in addition to migrating and modernizing their massive information and analytics workloads to AWS. She is obsessed with empowering organizations to unlock the complete potential of their information.

Vikas Omer is the Head of Knowledge & AI Resolution Structure for ASEAN at Amazon Net Companies (AWS). With over 15 years of expertise within the information and AI house, he’s a seasoned chief who leverages his experience to drive innovation and enlargement within the area. Vikas is obsessed with serving to prospects and companions succeed of their digital transformation journeys, specializing in cloud-based options and rising applied sciences.

Lorenzo Ripani is a Huge Knowledge Resolution Architect at AWS. He’s obsessed with distributed methods, open supply applied sciences and safety. He spends most of his time working with prospects all over the world to design, consider and optimize scalable and safe information pipelines with Amazon EMR.