Difference: Production100 (27 vs. 28)

Revision 282018-09-23 - MarcoCattaneo

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

Getting Productions to 100%

Line: 123 to 123
 1 row in set (0.00 sec)
Changed:
<
<
I discover this job is stalled. The job application ran to completion in the RAL queue when it was already in draining state before a downtime. Then it started to finalize, but I assume that, because the SEs were banned, the output went to Failover, from which it was picked up lately without problems. So, the output is now replicated and registered in the bookkeeping. The merged file even has a DataQuality Flag = 'OK'.
>
>
I discover this job is stalled. The job application ran to completion in the RAL queue when it was already in draining state before a downtime. Then it started to finalize, but I assume that, because the SEs were banned, the output went to Failover, from which it was picked up lately without problems. So, the output is now replicated and registered in the bookkeeping. The merged file even has a DataQuality Flag = 'OK'.
 However, I don't know why but the job was still in the queue, and stalled about 36 hours later, because the pilot was aborted.

So, what I did was again to mark these files as "Processed".

Line: 587 to 587
 as it's the only replica, the Bookkeeping replica is set to No:
> dirac-bookkeeping-file-metadata /lhcb/LHCb/Collision12/BHADRONCOMPLETEEVENT.DST/00019167/0002/00019167_00024559_1.BhadronCompleteEvent.dst

Changed:
<
<
FileName Size GUID Replica DataQuality RunNumber
>
>
FileName Size GUID Replica DataQuality RunNumber
 /lhcb/LHCb/Collision12/BHADRONCOMPLETEEVENT.DST/00019167/0002/00019167_00024559_1.BhadronCompleteEvent.dst 512931637 2016D74A-82E2-E111-A3B4-00266CF9B884 No OK 124919
 
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