Difference: ClusterWork (6 vs. 7)

Revision 72019-04-08 - RobinWatts

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Cluster work

Line: 112 to 112
 
   node <clustername>
   id <jobid>
Changed:
<
<
jobs timeouts
>
>
busy
  OK
Line: 121 to 120
 
node <clustername>
Inform the clustermaster which node is calling in.
Changed:
<
<
id <jobid>
Inform the clustermaster which job the node thinks it is running. If this mismatches, the clustermaster will tell the node to abort.

jobs <num jobs pending>
This tells the clustermaster how many jobs the node has been given to run that have not currently completed. When this number drops to 0, the clustermaster can consider giving the node another batch of jobs.
>
>
id <jobid>
Inform the clustermaster which job the node thinks it is running. If this mismatches, the clustermaster will tell the node to abort.
 
caps <capability string>
The node tells the clustermaster what it's capabilities are.

status <status string>
A status string for the node. Can be anything.
Changed:
<
<
busy
Inform the clustermaster that the node is currently busy doing previously allocated work (building, or uploading files).
>
>
jobs <num pending>
The number of jobs the server has been given, and has not queued yet. When this drops to zero, the clustermaster should consider giving the node more jobs, as capacity is sitting idle.

busy
Inform the clustermaster that the node is currently busy doing previously allocated work (building, running jobs, or uploading files).
 
failure <reason>
Inform the clustermaster that the node failed, and that failure logs have been uploaded. Negative reasons are considered fatal and should stop the job on all nodes. Values for reason include:
  • -1: Failed because of a build problem.
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright 2014 Artifex Software Inc