Just to be clear here: I too observed this using a 4.9.1 client and a 4.9.0rc server. The "placement" phase occurs before the client generates the tpc.key. That is passed to the source on the second open. Since it is not needed to match against the destination's client, the second open really serves no further purpose ... if I understand this correctly. Al ________________________________________________ Albert L. Rossi Application Developer & Systems Analyst III Scientific Computing Division, Data Movement Development FCC 229A Mail Station 369 (FCC 2W) Fermi National Accelerator Laboratory Batavia, IL 60510 (630) 840-3023 ________________________________ From: Albert Rossi Sent: Thursday, May 9, 2019 12:58:18 PM To: Yang, Wei; Michal Kamil Simon; xrootd-dev Cc: Dmitry O Litvintsev Subject: Re: delegation and the tpc.key Hi Wei, The client opens and closes the file on the source during the "placement" phase. What it no longer does (when there is delegation) is to open it again during the copy phase. So instead of two open/close requests on the source you only see one. Al ________________________________________________ Albert L. Rossi Application Developer & Systems Analyst III Scientific Computing Division, Data Movement Development FCC 229A Mail Station 369 (FCC 2W) Fermi National Accelerator Laboratory Batavia, IL 60510 (630) 840-3023 ________________________________ From: Yang, Wei <[log in to unmask]> Sent: Thursday, May 9, 2019 12:46:48 PM To: Michal Kamil Simon; Albert Rossi; xrootd-dev Cc: Dmitry O Litvintsev Subject: Re: delegation and the tpc.key Hi Michal, Is this a change in the client only? and is it after 4.9.1 was releases? I am using 4.9.1 client and a server (4.9.0rc5?) and I can see that the client opens file with both source and destination? I am just curious. I think the change is good but not sure when should I expect to see it. regards, -- Wei Yang | [log in to unmask] | 650-926-3338 ________________________________________ From: [log in to unmask] <[log in to unmask]> on behalf of Michal Kamil Simon <[log in to unmask]> Sent: Thursday, May 9, 2019 7:59 AM To: [log in to unmask]; xrootd-dev Cc: Dmitry Litvintsev Subject: RE: delegation and the tpc.key Hi Albert, That's correct, in case of third-party-copy with delegation we optimized away opening of the source and setting up the rendex-vous as the destination is now able to proceed on its own. Cheers, Michal ________________________________ From: [log in to unmask] [[log in to unmask]] on behalf of Albert Rossi [[log in to unmask]] Sent: 09 May 2019 16:11 To: xrootd-dev Cc: Dmitry Litvintsev Subject: delegation and the tpc.key Hi everyone, I have noticed something interesting about the behavior of the xrootd server/client on TPC with 4.9. I had not noticed this before because I had not looked at verbose debug output, since everything seemed to be working. What I notice is the following: 1. Where before the client (xrdcp) used to do an open on the source again during the copy phase, I no longer see this occurring. 2. At the same time, the destination server (i.e., the server-side xrdcp client) does not pass the tpc.key to the source server on open. I noticed this because my own logging was reporting "not a tpc open" at that point. Everything is working fine, but I just wanted to make sure what I am seeing is correct. Am I correct in concluding that if delegation has occurred, the xrootd server stops using the tpc token? Thanks, Al ________________________________________________ Albert L. Rossi Application Developer & Systems Analyst III Scientific Computing Division, Data Movement Development FCC 229A Mail Station 369 (FCC 2W) Fermi National Accelerator Laboratory Batavia, IL 60510 (630) 840-3023 ________________________________ Use REPLY-ALL to reply to list To unsubscribe from the XROOTD-DEV list, click the following link: https://urldefense.proofpoint.com/v2/url?u=https-3A__listserv.slac.stanford.edu_cgi-2Dbin_wa-3FSUBED1-3DXROOTD-2DDEV-26A-3D1&d=DwIFAg&c=gRgGjJ3BkIsb5y6s49QqsA&r=60rQ0HHqHmEY1P6VSdyuTQ&m=mgHMnrdr8mNViETnKNk7er_7SyLZdUJBtR4Hp4wtPEc&s=E8ljBCkCEaklKQwNmpRfKGjT50ewRxE4Hz9llgLLbaw&e= ________________________________ Use REPLY-ALL to reply to list To unsubscribe from the XROOTD-DEV list, click the following link: https://urldefense.proofpoint.com/v2/url?u=https-3A__listserv.slac.stanford.edu_cgi-2Dbin_wa-3FSUBED1-3DXROOTD-2DDEV-26A-3D1&d=DwIFAg&c=gRgGjJ3BkIsb5y6s49QqsA&r=60rQ0HHqHmEY1P6VSdyuTQ&m=mgHMnrdr8mNViETnKNk7er_7SyLZdUJBtR4Hp4wtPEc&s=E8ljBCkCEaklKQwNmpRfKGjT50ewRxE4Hz9llgLLbaw&e= ######################################################################## 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