The masterhost and port arguments specify the hostname and port number of the master application for work_queue_worker to connect. These two arguments become optional when the auto mode option is specified.
work_queue_worker can be run locally or deployed remotely on any of the grid or cloud computing environments such as SGE, Amazon EC2, Condor using sge_submit_workers(1), ec2_submit_workers(1), condor_submit_workers(1) respectively.
-a | Enable auto mode. In this mode the worker would ask a catalog server for available masters. |
-C <catalog> | |
Set catalog server to <catalog>. Format: HOSTNAME:PORT | |
-s | Run as a shared worker. By default the worker would only work on preferred projects. |
-d <subsystem> | |
Enable debugging for the given subsystem. Try -d all as a start. | |
-o <file> | |
Send debugging to this file. | |
-N <project> | |
Set the project name to <project>. | |
-t <time> | |
Abort after this amount of idle time. (default=900s) | |
-w <size> | |
Set TCP window size. | |
-i <time> | |
Set initial value for backoff interval when worker fails to connect to a master. (default=1s) | |
-b <time> | |
Set maxmimum value for backoff interval when worker fails to connect to a master. (default=60s) | |
-z <size> | |
Set available disk space threshold (in MB). When exceeded worker will clean up and reconnect. (default=100MB) | |
-v | Show version string. |
-h | Show this help message. |
% work_queue_worker master.somewhere.edu 9123To run work_queue_worker in auto mode with debugging turned on for all subsystems and to accept tasks only from a master application with project name set to project_A:
% work_queue_worker -a -d all -N project_A