Yahoo uses flexible virtual-machine rankings and Auto-Zone placement to maintain Managed Service for Apache Spark cluster provisioning.

Yahoo uses flexible virtual-machine configurations in Google Cloud’s Managed Service for Apache Spark, formerly Dataproc. Instead of requiring one fixed machine type, Yahoo supplies a ranked list of acceptable VM shapes so the service can search for available capacity.

Auto-Zone placement must also be enabled to search across zones within a selected region. Users can do this by passing a region or an empty zone string, allowing cluster provisioning to move beyond a single zone’s capacity constraints.

For autoscaled clusters, the acceptable machine types should have similar CPU-core counts and memory capacities, even when they belong to different VM families. Google said a consistent CPU-to-memory ratio across primary and secondary workers is important because the smallest ratio determines effective container sizing.

The configuration supports Yahoo’s analytics environment following its migration of on-premises Hadoop and big-data estates to Google Cloud. Its purpose is to reduce provisioning delays and manual intervention when a specific VM shape has constrained capacity, rather than to guarantee that every requested machine type is always available.