You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To allow the user to CANCEL any transfers (PUT or GET or DELETE).
How would this percolate through the system?
I think this is probably quite difficult but I am asked quite often by users to cancel JDMA transfers, usually when they don't have enough space at the target directory.
The text was updated successfully, but these errors were encountered:
Oooh interesting, I think this is doable before the transfer takes place via some logic in the nlds_worker, but once the transfer has started it might be more difficult. There's probably some kind of interrupt functionality for a given rabbit consumer but I'll need to have a looksie.
We could also have the transfer worker periodically check some "cancelled-jobs" database to check that the current transaction_id is still good to go, but this seems cumbersome...
Can we do this with interrupts? Or a cancel queue that the consumers check every time they go round the loop? (This would be expensive if lots of cancel messages in the queue)
To allow the user to CANCEL any transfers (PUT or GET or DELETE).
How would this percolate through the system?
I think this is probably quite difficult but I am asked quite often by users to cancel JDMA transfers, usually when they don't have enough space at the target directory.
The text was updated successfully, but these errors were encountered: