View source for Cluster Jobs

==Cluster Job Organization==

<h4>Batch location</h4>
Don't run your batches from your home directory.  A runaway
kluster job can quickly swamp the NFS server for the home directories
and thereby lock out all users.  Your batch is typically run from some /cluster/storeN/ filesystem.  Also, please make sure your umask is set to 002 rather than the more restrictive 022.  We need to have group write permission to everyone's directory so we can fix stuff when you are not available.

<h4>Input/Output</h4>
The most critical factor in designing your cluster jobs is to
completely understand where your input data is coming from,
where temporary files will be made during processing, and
where your output data results are going.  With several hundred
CPUs reading and writing data, it is trivially simple to make
life very difficult for the underlying NFS fileservers.  The ideal case is, your input data comes from one file server, your temporary files
are written to /scratch/tmp/ local disk space, and your output data
goes back to a different NFS server than where your input data
came from.  For the case of input data that will be used in a variety of cluster jobs over an extended period of time, it can be arranged to copy that data to local /scratch/ disk space on each cluster node.

<h4>Job Script</h4>
A properly constructed job is typically a small .csh shell script that begins:
<pre>
#!/bin/csh -fe
</pre>

The -fe ensures the script will run to completion successfully or exit
with an error if any of the commands fail.  Parasol is aware of the errors if a command exits with errors so it will know a job has failed because of that. You can see many script examples in the kent source tree make*.doc files where we document all of our browser construction work.

If a line in your job file is too long it will cause the hub to crash.  Each command, along with the header information, needs to fit in 1444 bytes.

<h4>Job Recovery</h4>
There will almost always be failed jobs for a variety of reasons.  The most important thing to do is design your jobs such that they have an atomic file presence indicator of successful completion.  The case is typically to make a job do all of its work on the /scratch/tmp/ filesystem, creating its result file there.  When it has successfully completed its work there, it does a single copy of the result file back to a /cluster/storeN/ filesystem, which is outside of the cluster and thus more permanent. The existence of that file result can be verified by parasol commands to determine if the job was successfully completed.  Parasol keeps track of the jobs that are successful or not.  To re-run the failed jobs, you merely do a 'para push' of the batch again, and the failed jobs will be retried. A job can be retried like this until it fails four times.  A gensub2 template example to check a result file:<pre>
{check out line+ &lt;result.file&gt;}</pre>
is used to tell parasol to check that file to verify job completion.

gensub2 template syntax:<pre>
{check 'when' 'what' &lt;file&gt;}
</pre>
where 'when' is either "in" or "out"<BR>
and 'what' is one of: "exists" "exists+" "line" "line+"<BR>
"exists" means file exists, may be zero size<BR>
"exists+" means file exists and is non-zero size<BR>
"line" means file may have 0 or more lines of ascii data and is properly line-feed terminated<BR>
"line+" means file is 1 or more lines of data and is properly line-feed terminated

<h4>Long Running Jobs</h4>
If you really must run jobs that will occupy a lot of CPU time, I would highly recommend instead, to redesign your processing to avoid that.  If you insist there is no other way, then you must use the cluster politely and use the para option -maxNode=N to limit the number of nodes your long-running jobs are going to occupy.  You have to leave the cluster in a state where it can do work for other users.  Typical job times are on the order of minutes or less, at the outside tens of minutes.


[[Category:Cluster FAQ]]