You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: seqware-distribution/docs/site/content/docs/6-pipeline/user-configuration.md
+96-109
Original file line number
Diff line number
Diff line change
@@ -64,112 +64,99 @@ After restarting Oozie, Oozie will use the listed error codes in combination wit
64
64
be retried in case of a specific error. For example, in the above jobs that return with an SGE error code of SGE137 will automatically be retried 30 or
65
65
OOZIE_RETRY_MAX times, whatever is higher. The actual error codes will likely be dependent on your site.
66
66
67
-
## Pegasus Workflow Engine Configuration
68
-
69
-
The SeqWare Pipeline project can (currently) use two workflow engines: 1) the Pegasus/Condor/Globus/SGE engine or 2) the Oozie/Hadoop engine. Each requires a bit of additional information to make them work (and, obviously, the underlying cluster tools correctly installed and configured). For the Pegasus engine you need a few extra files, referenced by the SW_PEGASUS_CONFIG_DIR parameter above:
70
-
71
-
### sites.xml3
72
-
73
-
<!-- see http://www.opinionatedgeek.com/DotNet/Tools/HTMLEncode/encode.aspx -->
This file is from Pegasus and the handle="clustername" is how you tell SeqWare which cluster to submit to. The setup of cluster resources in the sites.xml3 file is beyond the scope of SeqWare so we refer you to the [Pegasus documentation](http://pegasus.isi.edu/).
## STAGE ALL OUR EXECUTABLES OR USE INSTALLED ONES
152
-
pegasus.catalog.transformation.mapper = All
153
-
154
-
## CHECK JOB EXIT CODES FOR FAILURE
155
-
pegasus.exitcode.scope=all
156
-
157
-
## OPTIMIZE DATA & EXECUTABLE TRANSFERS
158
-
pegasus.transfer.refiner=Bundle
159
-
pegasus.transfer.links = true
160
-
161
-
# JOB Priorities
162
-
pegasus.job.priority=10
163
-
pegasus.transfer.*.priority=100
164
-
165
-
#JOB CATEGORIES
166
-
pegasus.dagman.projection.maxjobs=2
167
-
</code></pre>
168
-
169
-
The Pegasus properties file controls where the sites.xml3 file lives and a few
170
-
other Pegasus parameters (our tc.data and rc.data files in SeqWare are empty).
171
-
The most important parameter above is "dagman.retry=1" which controls how many
172
-
attempts should be made before job is considered failed in a workflow. In this
173
-
example "1" means it should be retried once before failing. There are other
174
-
parameters that might be useful for Pegasus, see the [Pegasus
175
-
documentation](http://pegasus.isi.edu/) for more information.
67
+
For versions of the oozie-sge plugin from 1.0.3 onwards, two kinds of error codes are possible. Error codes of the form SGE[0-9]+ refer to the exit status of the actual Bash scripts that form steps in your workflows. Error codes of the form SGEF[0-9]+ refer to the failure code of the SGE infrastructure itself.
68
+
69
+
For example, the following output from "qacct -j" refers to a workflow step which failed with an error code of 1 (which would correspond to SGE1 for the Oozie XML parameter above).
The following output from "qacct -j" refers to a workflow step where the actual qsub failed since a logging directory was unavailable (leading to a Eqw state). This would correspond to an Oozie error code of SGEF26.
0 commit comments