[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [HTCondor-users] proposed change in DAGMan



I think this is an excellent option. I think it would be best for it to be on by default because I think it is most useful for naïve users.

John Calley, Ph.D.
Genetics and Bioinformatics, Tailored Therapeutics
Eli Lilly and Company
DC0731, Lilly Corporate Center, Indianapolis, IN 46285 USA 
317.433.3399 (office) | 317.655.1534 (fax)
calley_john_n@xxxxxxxxx | www.lilly.com 

CONFIDENTIALITY NOTICE:  This e-mail message (including all attachments) is for the sole use of the intended recipient(s) and may contain confidential and privileged information.  Any unauthorized review, use, disclosure, copying or distribution is strictly prohibited.  If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.


-----Original Message-----
From: HTCondor-users [mailto:htcondor-users-bounces@xxxxxxxxxxx] On Behalf Of R. Kent Wenger
Sent: Wednesday, June 15, 2016 2:09 PM
To: htcondor-users@xxxxxxxxxxx
Subject: [HTCondor-users] proposed change in DAGMan

We are proposing a change in DAGMan behavior relative to node jobs that are on hold, and before implementing it, we wanted to get feedback from the HTCondor user community.

Right now, DAGMan will wait indefinitely for jobs that are on hold, even if *all* of the node jobs for the DAG are on hold and, therefore, no progress is being made.

The proposed change is that, if DAGMan is "stuck" because all queued node jobs are on hold (and there are no ready jobs, running PRE/POST scripts, etc.), DAGMan will consider this a failure and abort the DAG (which results in all queued node jobs being removed, and a rescue DAG being generated).

Users would be able to opt out of the new behavior via a configuration setting.

Please let us know what you think of this proposal...

Kent
--
R. Kent Wenger (wenger@xxxxxxxxxxx, 608-262-6627,
http://www.cs.wisc.edu/~wenger/)
Computer Sciences Department
University of Wisconsin-Madison
_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/