Notes relating to monitoring the Spring 2012 Full Pass7 Fermi Reprocessing project.
- Detailed configuration of project: https://confluence.slac.stanford.edu/display/~dragon/P202+-+Full+Pass7+Reprocessing
- CPU-intensive ROOT generation (full reconstruction) task
- Pipeline task: http://glast-ground.slac.stanford.edu/Pipeline-II/task.jsp?task=74630144&dataSourceMode=Prod (One top-level stream = One Fermi data run)
- Task directory: /nfs/farm/g/glast/u38/Reprocess-tasks/P202-ROOT
- Task control
- trickleStream.py - long-running script to monitor current batch usage, and submit new top-level streams. Run only one instance of this script! I run it on my desktop machine, comet.slac.stanford.edu (RHEL6-64 machine), piping the output into a log file,
- Starting trickleStream
(Select "NN" to be next number in sequence.)
$ cd /nfs/farm/g/glast/u38/Reprocess-tasks/P202-ROOT/config $ ./trickleStream.py > tslogNN.txt &
- Stopping trickleStream - this can, of course, be done by killing the process explicitly. Or, one can halt gracefully by creating a file called 'stop' in the config directory, e.g.,
$ touch stop
- Monitoring trickleStream - watch the log file, e.g.,
$ tail -f tslogNN.txt
- Starting trickleStream
- trickleStream.py - long-running script to monitor current batch usage, and submit new top-level streams. Run only one instance of this script! I run it on my desktop machine, comet.slac.stanford.edu (RHEL6-64 machine), piping the output into a log file,
- Job Step Failures
- Monitor failures from the main pipeline page for this task
- Typically there have been ~10-30 failures per day, mostly transient disk-access problems (NFS, xroot) solved by a single rollback.
- All rollbacks are manual (no automatic retries internal to task) – to prevent serious problems from creating run-away rollbacks.