Difference: ProductionDB (2 vs. 3)

Revision 32008-09-22 - GreigCowan

Line: 1 to 1
 
META TOPICPARENT name="ProductionProcedures"
Line: 144 to 144
 

# WMS job state prodDB input file state BK,LFC output file status Action
Changed:
<
<
1 Done/Completed Processed OK No action
2 Done/Completed Processed not OK file => Unused
3 Done/Completed Assigned/Unused OK file => Processed
4 Done/Completed Assigned/Unused not OK file => Processed; clean up BK, LFC?
>
>
1 Done Processed OK No action
2 Done Processed not OK file => Unused
3 Done Assigned/Unused OK file => Processed
4 Done Assigned/Unused not OK file => Processed; clean up BK, LFC?
 
5 Failed Processed OK WMS job => Done
6 Failed Processed not OK file => Unused
7 Failed Assigned/Unused OK clean up BK,LFC
Line: 157 to 157
 
11 Stalled Assigned/Unused OK ?
12 Stalled Assigned/Unused not OK ?
Added:
>
>
  • RUNNING : If jobs are RUNNING then we should just leave them alone until they fall into one of the above states.
  • COMPLETED : What should I do if jobs are COMPLETED ? Originally I was equating them with DONE. However, COMPLETED means that there are some files which have not yet finished transferring, in which case it is expected that the prodDB and LFC/BK could be in some inconsistent state.
  -- StuartPaterson - 08 Sep 2008 -- GreigCowan - 21 Sep 2008
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback