- Newest
- Most votes
- Most comments
Hello,
There could be the chance that you have turned off the termination protection
and enabled the auto termination
. Possibly when the core or task node goes to unhealthy state
due to the reasons like disk space utilized more than 80 %, Yarn mark those nodes unhealthy and exclude the node for scheduling the task. If this situation persist about an hour, then node will be decommissioned
and terminate the instance in case the termination protection policy is disabled.
You can refer the EMR instance-state log to confirm this, if the logging enabled for the cluster. You can refer the s3://logging bucket/<cluster-id>/node/<ec2-instance>/daemons/instance-state/instance-state-log*
. In this location, you can find the particular instance's OS statistics like the output of df -h, top cpu, top memory
and etc, that logged every 15 minutes of the state. Let me know if you have any queries on this.
Relevant content
- asked 9 months ago
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 2 years ago