Difference: Production100 (26 vs. 27)

Revision 272012-10-04 - unknown

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

Getting Productions to 100%

Line: 450 to 450
 fixed on 31/08/2012 solution here

Production with some Assigned files, though the Dirac job is reported as Done

Changed:
<
<
In production 18310 (Aug 2012) some files are in Assigned status and the relative jos status is Done:
>
>
In production 18310 (Aug 2012) and also in prod. 18117 ( see http://lblogbook.cern.ch/Operations/12057) some files are in Assigned status and the relative jos status is Done:
 
mysql> select ExternalStatus,ExternalID,TargetSE,CreationTime,LastUpdateTime from TransformationTasks where  TransformationID=18310 and TaskID in (15954,15957,10580,8055,73965) order by ExternalID;

Line: 489 to 490
 

Temporary Solution

Changed:
<
<
In such case, unfortunately, it is necessary to update the status directly on the Production Db, otherwise the input files will not be reset to Unused. Important: how to kill the job. Of course the job should be killed from job monitor. However, in this case it was not possible: killing the job from job monitor had as only effect to set the job killed in the Job db, but the status was not propagated to Production DB, where after hours the status was still Done.
>
>
In such case, the input files of the job should be reset to Unused using the command: dirac-transformation-reset-files. This will of course create an inconsistent situation in Production DB because the relative job is reported as Done.
  waiting for the fix.
 
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