Re: [Condor-users] Behavior of Condor jobs held for file transfer errors

[Dan Bradley <dan@xxxxxxxxxxxx>]

Removing jobs that are on hold can be achieved by using the 
periodic_remove expression in the job submit file or by the 
SYSTEM_PERIODIC_REMOVE expression in the submit machine condor 
configuration.

Example:

SYSTEM_PERIODIC_REMOVE = HoldReasonCode == 12 || HoldReasonCode == 14

The HoldReasonCodes are defined in the manual:

http://research.cs.wisc.edu/condor/manual/v7.6/10_Appendix_A.html#82773

--Dan

On 6/20/12 12:25 PM, Myung Cho wrote:
> Hi , I did a quick search for this topic but haven't found any
> relevant posts. Is there a way to change/specify the default behavior
> in Condor for jobs with file transfer errors? Our jobs with any error
> in file transfer, for example a missing file specified in
> transfer_output_files, seem to cause the job to be in held state for
> ever. Is there a way for the job to just complete with error? I rather
> see it finish with an error reported rather than have it just hang
> around in hold state.
>
> Thanks.
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/condor-users/