Changing 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.
- From the cluster management console, click .
- Select the resource group.
- Select the Time Intervals and Settings menu item.
- Click Slot allocation policy to expand it.
- Select the specific policy:
- Stacked
- Allocate slots from a single host before allocating from another host.
Hosts are selected in the order in which they appear in the resource group during VEMKD initialization. No decisive order for the host appears in the resource group. 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
- Allocate slots from the host with the highest number of free slots.
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
- Allocate all free slots from a host to one consumer.
Each host in the resource group is assigned to only one consumer at a time.
Note: If you have theEGO_ENABLE_CONSUMER_LEVEL_EXCLUSIVE=Ysetting in the ego.conf file (Configuring exclusive slots at the consumer level), then the exclusive slot allocation policy uses all free slots from a host, and additionally offers two exclusivity options:- Allocation level: Each host is only assigned to one allocation.
- Consumer level: Free slots from the host can be shared and assigned to any number of allocations, but only amongst a select set of consumers within an exclusive consumer group. These allocations can share free slots from the host.