2 Answers
- Newest
- Most votes
- Most comments
0
Hey There, Thank you for reaching out. We would request you to please provide the following information for us to look into this query further :
- Could you please let us know which services are you using and referring to (EC2, EMR, ASG, etc ) ?
- Kindly elaborate the issue that you’re encountering.
I see that you’ve mentioned that only in some cases the instances are stopped and clusters are terminated. Is any action taken from your end post which you observe this behaviour, please confirm ?
0
Please see details of the cluster creation. Thanks! https://paceuniversity-my.sharepoint.com/:w:/r/personal/pvasseur_pace_edu/_layouts/15/Doc.aspx?sourcedoc=%7B87C4C9C7-99C8-416E-AA67-A263C571177D%7D&file=EMR%20Cluster%20Steps.docx&action=default&mobileredirect=true
answered 6 months ago
Relevant content
- asked 6 months ago
- Accepted Answerasked a year ago
- Accepted Answerasked 10 months ago
- asked 8 months ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 9 months ago
When some of my students set up a cluster on Amazon Elastic MapReduce (EMR), the process automatically launches instances based on the specifications they chose during the cluster creation. The challenge arises when they try to stop these instances to control costs. Instead of halting, the instances end up being terminated, leading to the unexpected shutdown of the entire cluster.