Examples of using Instance groups in English and their translations into Spanish
{-}
-
Colloquial
-
Official
Not available for instance groups.
Task Instance Groups as Spot Instances. .
Autoscaling is a feature of managed instance groups.
Instance groups use the market type specified for the group. .
You configure the master and core instance groups as part of the AWS:: EMR::Cluster resource.
Manually add instances of the same type to existing core and task instance groups.
These instances must be in instance groups attached to the backend service as backends.
It also tracks the status of each task performed andmonitors the health of the instance groups.
If you launch your master and core instance groups as On-Demand Instances, their capacity is guaranteed for the run of the cluster.
For more information,see Create a Cluster with Instance Fleets or Uniform Instance Groups.
Launching task instance groups as Spot Instances is a strategic way to expand the capacity of your cluster while minimizing costs.
Fundamentally, instance fleets use a different method than uniform instance groups to launch instances. .
When you launch one or more task instance groups as Spot Instances, Amazon EMR provisions as many task nodes as it can, using your maximum Spot price.
For more information about these configurations,see Create a Cluster with Instance Fleets or Uniform Instance Groups.
Your choice to use instance groups or instance fleets in your cluster determines how you can change instance purchasing options while a cluster is running.
Use the EbsConfiguration property to configure Amazon Elastic Block Store storage volumes for your Amazon EMR clusters or instance groups.
There are several ways to add EC2 instances to a cluster,which depend on whether you use the instance groups configuration or the instance fleets configuration for the cluster.
Master node- Manages the cluster, coordinating the distribution of the MapReduce executable andsubsets of the raw data, to the core and task instance groups.
If you choose uniform instance groups, the instance type and purchasing option apply to all EC2 instances in each instance group, and you can only specify the purchasing option for an instance group when you create it.
Typically, you would only run the master node as a Spot Instance if you are running the entire cluster(all instance groups) as Spot Instances. .
Running the master and core instance groups as on-demand ensures that your data is persisted in HDFS and that the cluster is protected from termination due to Spot market fluctuations, while providing cost savings that accrue from running the task instance groups as Spot Instances. .
If you are running a cluster for which lower cost is more important than time to completion, but losing partial work is not acceptable,launch the master and core instance groups as on-demand and supplement with one or more task instance groups of Spot Instances. .
For instance, group the items on any list into like categories.
For autoscaling, the maximum number of EC2 instances in an instance group.
Set up automatic scaling in Amazon EMR for an instance group, adding and removing instances automatically based on the value of an Amazon CloudWatch metric that you specify.
Because each type of instance group plays a different role in the cluster, the implications of launching each instance group as Spot Instances vary.
When you launch an instance group either as on-demand or as Spot Instances, you cannot change its classification while the cluster is running.
To change an On-Demand instance group to Spot Instances or vice versa, you must terminate the cluster and launch a new one.
When you launch the master instance group as a Spot Instance, the cluster does not start until that Spot Instance request is fulfilled.
You cannot shrink the size of the core instance group in a running cluster by reducing the instance count.