Hi Globus User Discussion Group,
We have a user who submitted a Globus transfer task (multiple subdirectories, recursive, checksum copy) via the Globus WebUI. It appears that at the time that he submitted the transfer certain files existed at the source endpoint and were added to the transfer task, but by the time Globus attempts to transfer the file, it no longer exists. Globus performs a file existence check and reports ‘file not found’, as it should, but the transfer task then no longer makes progress because it does not seem to able to skip the file that is now missing at the source endpoint.
Is there a way in Globus to indicate a timeout after which Globus will move on to attempting to transfer the next file in the transfer task? Alternately, is there a way to request that Globus ignore files (or, produce an error/warning and continue) in its transfer task list that are no longer found? Is the user’s only recourse to cancel and resubmit the entire transfer request?
I’ve looked through the Globus Transfer API and haven’t found a transfer specification field that might be relevant.
Thanks in advance!
Michele
--
To unsubscribe from this group and stop receiving emails from it, send an email to user-discuss...@globus.org.
Our team just informed me that we are working on enhancements to transfer tasks which include the ability to skip rather than retry FileNotFound errors, and to list files which were skipped after the task completes.
Hi Stephen and Jonathan,
Thank you both for your suggestions (sync types and setting deadlines for transfer tasks). I will subscribe to developer-discuss to watch for any Globus feature releases.
Thanks again!
Michele