Re: [HTCondor-users] splitting CondorCE routes over mutiple configs

[John M Knoeller <johnkn@xxxxxxxxxxx>]

Hi Thomas, 

What you propose is fine.

The main effect would not be on the job router itself, but on tools like condor_status and condor_q which also read the configuration. 

It is just a tiny bit slower to read multiple small files than it is to read a single large file,  but you would have to have hundreds of routes to notice any difference.

The tradeoff in ease of configuration management is almost certainly worth it.

-tj

---

From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of Thomas Hartmann <thomas.hartmann@xxxxxxx>
Sent: Wednesday, March 10, 2021 8:05 AM
To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
Subject: [HTCondor-users] splitting CondorCE routes over mutiple configs

 

Hi all,

quick question:
since the CondorCE route examples stack all the route into one
_expression_, I wonder, if there are any 'contraindications' to split
instead the routes into smaller chunks like [1]?

Cheers,
   Thomas

[1]

 > 90_01_myroute1.conf
MYROUTE1 @=end
[
   TargetUniverse = 5;
   name = "My Test Route 1";
]
@end


 > 90_02_myroute2.conf
MYROUTE2 @=end
[
   TargetUniverse = 5;
   name = "My Test Route 2";
]
@end


JOB_ROUTER_ENTRIES = $(JOB_ROUTER_ENTRIES) $(MYROUTE1) $(MYROUTE2)