Closed merictaze closed 9 years ago
Hi Tony,
as far as I can tell, this issue is caused by the fact that the BlockDelete agent was not changed in 4.1.3
The required change was reported in this ticket:
https://github.com/dmwm/PHEDEX/issues/931#issuecomment-26936046
"2) for the BlockDelete agent: change the node filter in the "merge into t_dps_block_delete" statement in the same way, excluding only T0/T1_Buffer/MSS nodes, allowing T1_Disk nodes."
Cheers Nicolo'
Hi Tony,
After deploying PhEDEx 4.1.4 in prod, I found a new bug Issue is the following:
I think the scenario would be the same even if FNAL_Disk was subscribed to the sample, and approve move request as a source site to be cleaned up. Blocks&Files which are injected after the source deletion approved will continue to stay on disk.
Cheers, Meric
[1] dataset time_create https://cmsweb.cern.ch/phedex/datasvc/xml/prod/data?dataset=/QCD_Pt-15to3000_Tune4C_Flat_14TeV_pythia8/GEM2019Upg14DR-Phase1age1kJan23_PU140BX25_PH1_1K_FB_V3-v1/GEN-SIM-RECO
[2] https://cmsweb.cern.ch/phedex/prod/Request::View?request=432853
Hi all,
https://github.com/dmwm/PHEDEX/commit/ee621088f3586f2a8e895165c2a0b39d70bfb6d6
this should fix the edge-case reported by Meric, more detailed explanation here
https://hypernews.cern.ch/HyperNews/CMS/get/comp-ops/2001/3/2/1/1/1/1/1.html
Hi,
4.1.5pre3 built with this fix, in testing.
N
Fix deployed in production in Sep 2015 with PhEDEx 4.1.5 - closing.
Nicolò
Hi Tony,
I tested move subscription on Dev instance after updating it to 4.1.3, but it did not run as expected.
I created a move request for the data[1] to T1_UK_RAL_MSS. I was expecting that it will be removed from all nodes except MSSes. However, it was removed from only T2_CH_CERN and T3_GR_Demokritos [2].
Cheers, Meric
[1] https://cmsweb.cern.ch/phedex/datasvc/xml/dev/blockreplicas?block=/Dev/LoadTest/Alpha%231
[2] https://cmsweb.cern.ch/phedex/test/Activity::Deletions?reqfilter=&node=.*&state=any&blockfilter=%2FDev%2FLoadTest%2FAlpha.*&.submit=Update#