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

[John M Knoeller <johnkn@xxxxxxxxxxx>]

This sounds like 

    JOB_ROUTER_ROUND_ROBIN_SELECTION  = true

is configured in the CE.   The default is false.  

    condor_ce_config_val -v JOB_ROUTER_ROUND_ROBIN_SELECTION 

Will show if that is the case.

Alternatively, there is a limit on the total number of jobs that can be routed to DESYNAF and that limit

is being hit. 

    condor_ce_job_router_info -config

should show any limits on the routes.

-tj

---

From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of Thomas Hartmann <thomas.hartmann@xxxxxxx>
Sent: Wednesday, December 3, 2025 9:26 AM
To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
Subject: [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=""> vs
12/03/25 15:38:32 JobRouter: Found candidate job
src="">
[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