Bugzilla – Bug 4166
Ability to modify the transfers of an RFT object
Last modified: 2006-01-19 12:29:23
You need to
before you can comment on or make changes to this bug.
The endpoint for an RFT transfer may be a gridftp server listening on a dynamic
port. If that server
crashes and restarts, but is unable to rebind to the same port, there is no way
to recover the transfer.
The whole RFT object must be deleted and a new one created. It would be nice if
the client could modify
the endpoints of transfers of an existing RFT object for this situation.
This feature becomes especially useful in the context of WS-GRAM. When the
scenario described above
occurs on the RFT object for staging out a GRAM job's files, the entire job
must be canceled and
resubmitted, potentially losing many hours or day of computation.
Condor-G is one GRAM client that runs a gridftp server on a dynamic port. I
globusrun-ws will soon be another.
This feature was initially request a while ago, but wasn't entered into