Changes between Version 23 and Version 24 of External_Supercomputing_Notes

Timestamp:

Feb 4, 2014, 6:04:42 PM (12 years ago)

Author:

watersc1

Comment:

--

External_Supercomputing_Notes

@@ -7 +7 @@
 I still think holding the remoteRun fixed to a single mrun command is best.  However, instead of the remoteRun defining everything, it needs to have child rows in a different table (remoteExp?) that points to the stage, stage_id, file lists, etc that are contained in the remoteRun.  This will need some work to redevelop.
 
+Further thinking leads me to the conclusion that with stages of this size, it's likely to be completely impractical to do much manual reverts.  I'm beginning to think that if a command fails twice (is run, fails, is attempted again when that state is found, and fails again), it should just be abandoned and ignored.  stask doesn't current retry failed jobs (it notes the return code, but does no logic on it).
 == 2014-02-03 ==