for dataset migrated from global to local DBS use location from global

dmwm / CRAB2

CRAB2

2 stars 11 forks source link

for dataset migrated from global to local DBS use location from global #1055

Closed belforte closed 10 years ago

belforte commented 10 years ago

when dataset is migrated it is still accessible, but DB3 has no location. Or even worse a bad one like the SE where the file was initially created and then deleted. Somehow in this case DBS2 was apparently falling back silently to PhEDEx.

Maybe even as simple as tell user to make sure they really want to use local DBS, or enforce that only USER tier can be accessed in phys03 ?

belforte commented 10 years ago

maybe always look in phedex first ?

belforte commented 10 years ago

so:

look in phedex first
if dataset is not known to phedex AND am using phys0x DBD, use origin_site_name from DBS, else barf as 'unknown location'