There are several way to control which hosts the supervisor will select when deciding where to start job instances on the farm. These are based on restrictions that can be defined for both jobs and Workers.
- 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
| Include Page |
|---|
| _restrictionsSyntax |
|---|
| _restrictionsSyntax |
|---|
|
HostsQube! allows users to specify a list of hosts, for the job to run on. This is a comma-delimited list of hostnames. You can also specify a list of hosts on which the job is restricted from running.
Examples
| Command | Meaning |
|---|
% qbsub --hosts "qb001,qb002" command | Run 'command' on hosts called qb001 and qb002 |
% qbsub --omithosts "qb001,qb002" command | Prevent 'command' from running on qb001 or qb002 |
Host GroupsQube! allows the administrator to organize the farm into clusters or host groups. These groups have no hierarchy, and hosts are allowed membership in multiple groups. In order to restrict a job to a specific set of hosts, the user may specify a set of groups to restrict the job to. This goes into the 'group' field of the job. Similarly to Hosts, it is also possible to omit groups from consideration.
Examples
| Command | Meaning |
|---|
% qbsub --groups "vfx,character" Render my/file.ma | Render the Maya file called file.ma on any host in the 'vfx' or 'character' groups |
% qbsub --omitgroups "vfx,character" command | Run 'command' on any host not in the 'vfx' or 'character' groups |
Host OrderSee Also
supervisor_default_hostorder
worker_cluster
...