There are several way to control which hosts the supervisor will select when deciding where to start job instances on the farm.
Hosts: Send only to an explicit set of workers
Host Groups: Send only to an explicit pre-defined group of workers
Host Order: Select hosts in a certain preferential order
| Anchor | ||||
|---|---|---|---|---|
|
...
A restriction is really defined as a "filter" for hosts based upon information in the queuing algorithm; the values are one or more cluster names. In the priority/cluster queuing system, a user specifies their restrictions by directory structure format:
/[<segment>/][<segment>/][+|*]
- + means all hosts at that level and below in the hierarchy.
- * means only hosts at that level.
| Note |
|---|
The restriction value is actually evaluated as an expression, and is specified in a "this cluster OR that cluster OR the other cluster" type of string, with the "||" symbol to mean OR |
Example
Allows hosts/jobs in /hello/world, but do not include lower levels:
/hello/world
Allows hosts/jobs in /hello/world and all levels below:
/hello/world/+
Allows only hosts/jobs below /hello/world/… but not including /hello/world:
/hello/world/*
Allows hosts in /hello or /goodbye:
/hello || /goodbye
| Include Page | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
Qube allows users to specify a list of hosts, for the job to run on. This is a comma-delimited list of hostnames.
...