[Chtc-users] Changes to condor_q output, happening TODAY!

[chtc-users@xxxxxxxxxxx]

Hello Again,

This message is for users of our high throughput compute (HTC) system, where jobs are submitted using the HTCondor scheduler.

This is a reminder that the output to "condor_q" commands will change today, such that jobs are grouped according to batch name, dag, or executable (in the event that no batch name has been indicated in the submit file).ÂThe change will take place onÂsubmit-3.chtc.wisc.eduÂandÂsubmit-5.chtc.wisc.eduÂat around 4pm today.

More details are listed farther below in the email we sent last week. We have even produced a new CHTC online guide that covers various ways of using condor_q, and in light of the new batched output:

http://chtc.cs.wisc.edu/condor_q

As always, please send any questions or comments toÂchtc@xxxxxxxxxxxÂ(instead of replying directly to this email). We hope you find the new queue format to be easier to view and navigate when you've submitted many jobs and/or batches of work. As members of the CHTC user community, you're getting access to these new features before they're available for worldwide users of HTCondor!

Cheers,

Your CHTC Team

On Wed, Jul 13, 2016 at 9:04 AM, <chtc-users@xxxxxxxxxxx> wrote:

Greetings CHTC users!

This message is for users of our high throughput compute (HTC) system, where jobs are submitted using the HTCondor scheduler. Â

Starting next Tuesday, July 19, the default output of the condor_q command will be significantly different, based on recent updates to HTCondor. Â

Currently, condor_q has an option called "-batch" which will display your jobs in groups, listing the current number of jobs running, held, idle, and completed. You can see what this looks like by running:

    condor_q -batch

As of July 19, this batched display option will become the default.ÂÂ

HTCondor will group jobs automatically by batch name (new), by DAG or by the sameÂexecutable. You can indicate which jobs belong to the same group, yourself, by either:Â

• adding the following line to any submit files that are part of the same group of jobs:Â
• batch_name = mybatchname
• using the following option with condor_submit:Â
  
• $ condor_submit submit.file -batch-name mybatchname

To display more detailed condor_q output (where each job is listed on a separate line), you can use the batch name or any existing grouping constraint (ClusterId, other "-constraint" option) and the "-nobatch" flag.Â

   condor_q -nobatch 123456

   condor_q -nobatch -dag 123457

   condor_q -nobatch -constraint 'JobBatchName == "mybatchname"'

For complete details, we have an online guide detailing the new condor_q behavior (and other useful condor_q options!) here:Âhttp://chtc.cs.wisc.edu/condor_q

Let us know if you have any questions or concerns by emailing chtc@xxxxxxxxxxx. Â

Cheers,

Your CHTC team

_______________________________________________
Chtc-users mailing list
Chtc-users@xxxxxxxxxxx
To unsubscribe send an email to:
chtc@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/chtc-users