60 likes | 235 Views
Online/Offline Data Transfer Discussions. FC API. ADTDB. LFC. PIT->Castor. DIRAC @ PIT. ONLINE SYSTEM. DISET. RequestDB Svc. Request Database. Data Mover. Online Run Database. DISET. Online Storage. Transfer Agent. Replica Manager. CERN-IT. Castor Storage. File movement.
E N D
FC API ADTDB LFC PIT->Castor DIRAC @ PIT ONLINE SYSTEM DISET RequestDB Svc Request Database Data Mover Online Run Database DISET Online Storage Transfer Agent Replica Manager CERN-IT Castor Storage File movement Request movement rfcp/lcg-utils
Online ‘Removal’ DIRAC @ PIT ONLINE XML-RPC SERVER xml-rpc Replica Manager DISET? Transfer Agent CERN-IT DISET Online Removal Agent RequestDB Svc Request Database DISET AutoDataTransfer Database Request movement File removal
What is currently working.. • Rfcp file to castor, file registered in AdtDB+LFC • File migration status is checked by OnlineRemovalAgent • Once migrated removal request sent to gateway DIRAC • Gateway DIRAC sends message to data mover
Possible transfer methods • RFIO – rf* • Pros: • md5 support and returned on success • RFIO storage class already implemented • Cons: • Doesn’t go through SRM • Grid tools – lcg-cp • Pros: • Standard utilities used for file upload • Upload through SRM interface • Cons: • No md5 (G-U-C underneath) • SLC4/64bit NOR SLC4/32bit (currently) supported
Possible integrity checks • Md5 • Can check file on castor disk pool against online md5 • If inconsistent • remove file and send message to RunDB (retried) • Can store md5 in file catalogue • Possible to use for future checking of data integrity • Castor checksum • Possible (someone tell me how) to get checksum from castor • If we can generate the same checksum online • Once file is migrated compare • If matches then file can be removed online • If not remove file and send message to RunDB (retried) • Using rfio we can do both • Using grid tools only the latter • During March test generate statistics on occurrences of checksum mismatches -> eventual strategy.