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

Re: [HTCondor-users] Fwd: Manually Setting ClusterID


Many thanks for the reply!

I had also asked the same question to StackOverflow and, in the spirit of the site looked you up, did not found you and as such answered myself giving credit where credit is due.

If you disagree with it being posted or want to remove your name / company please let me know.

Thank you very much,


On Tue, Nov 11, 2014 at 2:43 PM, Ben Cotton <ben.cotton@xxxxxxxxxxxxxxxxxx> wrote:

Good news! SCHEDD_CLUSTER_INITIAL_VALUE is the schedd setting you
want. From the manual:

An integer that specifies the initial cluster number value to use
within a job id when a job is first submitted. If the job cluster
number reaches the value set by SCHEDD_CLUSTER_MAXIMUM_VALUE and
wraps, it will be re-set to the value given by this variable. The
default value is 1.

It might be a good idea, if it's possible, to modify your external
services to use GlobalJobId to identify jobs instead of just the
straight job id. I have a patch submitted (poke, poke, Todd) to add
the following to the ClassAd reference:

A globally-unique job identifier. Contains the queue name, JobId, and
schedd start time (in seconds since Jan 1, 1970) joined by #. For
example, submit.example.com#152.3#1358363336

The inclusion of the schedd start time helps prevent issues like
you're encountering (plus eventually the odometer will reset on your
cluster ID anyway).


Ben Cotton
main: 888.292.5320

Cycle Computing
Leader in Utility HPC Software

twitter: @cyclecomputing
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting

The archives can be found at: