LISTSERV 16.5 - XROOTD-DEV Archives

@mpatrascoiu thank you for the useful info.

FTS (in fact, this is all done at the Gfal2 level) requests the checksum to be computed at the end of the transfer part. The checksum computation is included in the copy(..) operation

Is there a way to verify this happens? The xrootd-hdfs plugin would save checksums in separate files (/cksums), but the new plugin stores it in xattr which should be faster.

From the logs I see

220714 00:00:22 4458 7dc42260.0 ofs_close: use=1 fn=/xrootd/cms/store/mc/Run3Summer21DRPremix/TT_TuneCP5_14TeV-powheg-pythia8/GEN-SIM-DIGI-RAW/120X_mcRun3_2021_realistic_v6_ext1-v5/40000/3d60585b-0bb8-42d5-993b-3115f168d728.root
<snip>
220714 00:00:22 7229 7dc42260.4100:[log in to unmask] Xrootd_Protocol: 0000 Bridge waiting for resp; sid=0 wt=600 (Job scheduled.)
220714 00:00:22 7229 Xrd_Sched: running chksum inq=0
220714 00:00:22 7229 Xrootd_jobXeq: Job chksum /xrootd/cms/store/mc/Run3Summer21DRPremix/TT_TuneCP5_14TeV-powheg-pythia8/GEN-SIM-DIGI-RAW/120X_mcRun3_2021_realistic_v6_ext1-v5/40000/3d60585b-0bb8-42d5-993b-3115f168d728.root started

# checksum logs
2022-07-14 00:00:23,337 [xrdsum]  DEBUG: No checksum found in metadata (user.xrdsum.adler32) for file /xrootd/cms/store/mc/Run3Summer21DRPremix/TT_TuneCP5_14TeV-powheg-pythia8/GEN-SIM-DIGI-RAW/120X_mcRun3_2021_realistic_v6_ext1-v5/40000/3d60585b-0bb8-42d5-993b-3115f168d728.root: At least one of the attributes provided was not found.
2022-07-14 00:00:23,346 [xrdsum]  DEBUG: Reading /xrootd/cms/store/mc/Run3Summer21DRPremix/TT_TuneCP5_14TeV-powheg-pythia8/GEN-SIM-DIGI-RAW/120X_mcRun3_2021_realistic_v6_ext1-v5/40000/3d60585b-0bb8-42d5-993b-3115f168d728.root in chunks of 134217728 bytes (out of 3682337619)
2022-07-14 00:00:59,638 [xrdsum]  DEBUG: No checksum found in metadata (user.xrdsum.adler32) for file /xrootd/cms/store/mc/Run3Summer21DRPremix/TT_TuneCP5_14TeV-powheg-pythia8/GEN-SIM-DIGI-RAW/120X_mcRun3_2021_realistic_v6_ext1-v5/40000/3d60585b-0bb8-42d5-993b-3115f168d728.root: At least one of the attributes provided was not found.

Which kinda looks like it is doing the right thing.

So there should be no reason for FTS to not get a response quickly.
I will add more debug info.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1736#issuecomment-1191311383", "url": "https://github.com/xrootd/xrootd/issues/1736#issuecomment-1191311383", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1