Configuration to change the slot allocation policy

When you change the slot allocation policy, the change only applies to future allocations, not existing ones. For example, if changing the slot allocation policy for the ManagementHosts resource group, any started services remain on hosts from which slots have been allocated and are not redistributed until the services are restarted.

Configuration

Configuration source

Setting

Behavior

Slot allocation policy

From the Platform Management Console Dashboard:

  1. Consumers > Consumers & Plans > Resource Plan

  2. Select the resource group.

  3. Select Time Intervals and Settings > Show Advanced Settings from the drop-down menu.

  4. Click Slot allocation policy to expand it.

  5. Select the specific policy.

  • Stacked. Allocate slots from a single host before allocating from another host.

  • Balanced. Allocate slots from the host with the highest number of free slots.

  • Exclusive. Allocate all free slots from a host to one consumer.

  • Stacked.

    Hosts are selected in the order in which they appear in the resource group during vemkd initialization. CPU slots are allocated from a single host until all CPU slots on that host are allocated, before slots are allocated from another host.

  • Balanced.

    Hosts are selected according to the number of free CPU slots. The host in the resource group with the highest number of CPU slots is selected first. CPU slots are equally allocated from hosts.

  • Exclusive.

    Each host in the resource group is assigned to only one consumer at a time.