| work_queue_factory(1) | Cooperative Computing Tools | work_queue_factory(1) |
work_queue_factory - maintain a pool of Work Queue workers on a batch system.
work_queue_factory -M <project-name> -T <batch-type> [options]
work_queue_factory submits and maintains a number of work_queue_worker(1) processes on various batch systems, such as Condor and SGE. All the workers managed by a work_queue_factory process will be directed to work for a specific master, or any set of masters matching a given project name. work_queue_factory will automatically determine the correct number of workers to have running, based on criteria set on the command line. The decision on how many workers to run is reconsidered once per minute.
By default, work_queue_factory will run as many workers as the indicated masters have tasks ready to run. If there are multiple masters, then enough workers will be started to satisfy their collective needs. For example, if there are two masters with the same project name, each with 10 tasks to run, then work_queue_factory will start a total of 20 workers.
If the number of needed workers increases, work_queue_factory will submit more workers to meet the desired need. However, it will not run more than a fixed maximum number of workers, given by the -W option.
If the need for workers drops, work_queue_factory does not remove them immediately, but waits to them to exit on their own. (This happens when the worker has been idle for a certain time.) A minimum number of workers will be maintained, given by the -w option.
If given the -c option, then work_queue_factory will consider the capacity reported by each master. The capacity is the estimated number of workers that the master thinks it can handle, based on the task execution and data transfer times currently observed at the master. With the -c option on, work_queue_factory will consider the master's capacity to be the maximum number of workers to run.
If work_queue_factory receives a terminating signal, it will attempt to remove all running workers before exiting.
On success, returns zero. On failure, returns non-zero.
Suppose you have a Work Queue master with a project name of "barney". To maintain workers for barney, do this:
work_queue_factory -T condor -M barney
To maintain a maximum of 100 workers on an SGE batch system, do this:
work_queue_factory -T sge -M barney -W 100
To start workers such that the workers exit after 5 minutes (300s) of idleness:
work_queue_factory -T condor -M barney -t 300
If you want to start workers that match any project that begins with barney, use a regular expression:
work_queue_factory -T condor -M barney.-t 300
If running on condor, you may manually specify condor requirements:
work_queue_factory -T condor -M barney --condor-requirements 'MachineGroup == "disc"' --condor-requirements 'has_matlab == true'
Repeated uses of condor-requirements are and-ed together. The previous example will produce a statement equivalent to:
requirements = ((MachineGroup == "disc") && (has_matlab == true))
Use the configuration file my_conf:
work_queue_factory -Cmy_conf
my_conf should be a proper JSON document, as:
{
"master-name": "my_master.*",
"max-workers": 100,
"min-workers": 0
}
Valid configuration fields are:
master-name foremen-name min-workers max-workers workers-per-cycle task-per-worker timeout worker-extra-options condor-requirements cores memory disk
The capacity measurement currently assumes single-core tasks running on single-core workers, and behaves unexpectedly with multi-core tasks or multi-core workers.
The Cooperative Computing Tools are Copyright (C) 2005-2019 The University of Notre Dame. This software is distributed under the GNU General Public License. See the file COPYING for details.
| CCTools 7.1.2 FINAL |