Data deletion policy for "obsoleted" and "old and good" derivations is being discussed at CREM and PC meetings. Technicalities for a possible change for not deleting "old and good" at LOCALGROUPDISKs will be discussed at the ProdSys2 meeting next Tuesday, Feb. 9th
Reprocessing
2012 Jet-MET - 1/3 done last week. Went smoothly. Launching second 1/3 now
No news on 2015 reprocessing
CRC/ADCoS report
Normal production activity - mainly simulation, pile-up, and analysis
T0 activity - Ongoing tests of new release 20.7.X to measure performances and optimise CPU efficiency and workflows
WORLD cloud - Tasks assigned, tests ongoing (mainly T1 as nucleus, few T2s)
Lot of pending analysis jobs (Moriond around the corner...) but lower level of activity than usual
Seems due to ATLAS pilot factory inducing CREAM-CE instability
Impacting mostly NL (no jobs), DE and RU
Pilot factories that tried to create job leases with lease creation time in the past inducing high load in CREAM database and pilots failing
Experts working on solution...
RAL also blacklisted because of problem on disk server
WORLD cloud - Tasks stuck because sent to a nucleus with data but not enough memory to run the task
Request sent to get panda monitoring with sites chosen as nucleus/satellites
Fair amount of data consolidation causing some T1 full issues + Data staging for 2012 reprocessing
FZK and PIC datadisks full (almost no secondary) - rebalanced to NDGF
CERN SCRATCHDISK filled up during the weekend
Caused by tasks from one user using the entire 2012 AOD data as input (valid use case? - there was some discussion on this point), which is only on CERN tape. Input data were staged from tape and put on scratchdisk
Some DPD tasks failing because AODtoDAOD got a SIGABRT signal (exit code 134)
Some tasks failing at BOINC
Occasional issues with CVMFS Stratum 1 and PanDA servers
ADCoS senior shifter coverage ok but no ADC experts this week
ACTION ITEM FOR SITES: Sites please regularly check and confirm that your historical APEL data has been published and looks correct when comparing with batch system utilization
See example steps circulated by D. Qing (20100406)