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

[HTCondor-users] CondorCE: jobs taking different routes albeit the same route condition are fulfilled



Hi all,

I am sometimes observing, that jobs on a test CE are taking different routes although the conditions should be the same for taking a specific route. I.e., some jobs go via the `DESYNAF` as intended but some go via the default `Condor_Pool` route [1] The two example CE jobs in [1] have both the same `atlasnf1` owner [2] mapped - which is actually the sole requirement for the `DESYNAF` route [3], so that I would expect both jobs to match to this route, or?

Cheers,
  Thomas

[1]
12/03/25 16:05:53 JobRouter: Found candidate job src=114376.0,route=DESYNAF
vs
12/03/25 15:38:32 JobRouter: Found candidate job src=114316.0,route=Condor_Pool

[2]
[root@naf-htc-preprod-ce01 config.d]# sdiff /tmp/114376.DESYNAF.ads /tmp/114316.CondorPool.ads | grep -i owner Owner = "atlasnf1" Owner = "atlasnf1"

[3]
[root@naf-htc-preprod-ce01 config.d]# cat 99_nafroute.conf
JOB_ROUTER_ROUTE_DESYNAF @=end
  UNIVERSE VANILLA
  REQUIREMENTS Owner == "atlasnf1"
  ...
@end

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature