While primary control of Qube Remote Control is the Supervisor, the Worker is responsible for making monitoring the remote host and executing jobs dispatched by the Supervisor. Like the Supervisor, once the Worker is configured, there is little need to return to its configuration.
Workers can be configured locally on the each system or centrally from the Supervisor. One can configure all Worker parameters locally. However, with larger farms, the Worker configuration process can become cumbersome, so Qube is designed to allow for a minimal configuration local to the host, in favor of a centralized configuration on the Supervisor. The qbwrk.conf file on the Supervisor is configuration file is the most efficient place to all your Worker configurations. Since this file is located only on the Supervisor, it allows an administrator to define settings for many Workers in central location.A Supervisor autodiscovery process is used by Qube as a means to quickly identify the Supervisor without any local configuration necessary. If the Supervisor Local configuration is done in the local qb.conf file; central configuration is done with a qbwrk.conf file on the Supervisor.
Configuration Topics
| Children Display |
|---|
Worker Startup Process
When a Worker starts up, it performs the following actions to configure itself and locate the Supervisor.
- Start up and initialize with default configuration settings.
- Read the local
qb.confconfiguration file, and override the default configuration with any settings it finds in the file. - If there is no Supervisor set in the configuration file, the Worker will send out a broadcast requesting a Supervisor to identify itself. (Supervisor autodiscovery)
- Contact the Supervisor for additional configuration settings located in the Supervisor's central Worker configuration file (
qbwrk.conf). - The Supervisor can be directed to use a different file for central Worker configuration - see supervisor_worker_configfile
Note that each consecutive configuration setting will override any previous configuration setting. This behavior can be modified or reversed by changing the worker_lookup setting.
Supervisor Autodiscovery
As described above, if the Supervisor isn't explicitly set in the Worker's configuration file, it will use autodiscovery to find the Supervisor host name and IP address. However that Supervisor and Worker must be on the same network subnet. Once it has that information it can then gather configuration from the Supervisor and continue the startup configuration process.
childrenIn general, it is preferable to explicitly name the Supervisor however, since this speeds job startup time and reduces network traffic slightly.