On Jun 10, 2008, at 2:36 AM, Enol Fernández wrote:I am trying to do matchmaking with Condor-C advertising to the collector a ClassAd similar to the one found in the Condor manual in http://www.cs.wisc.edu/condor/manual/v7.0/5_3Grid_Universe.html#SECTION00637200000000000000
MyType = "Machine"
TargetType = "Job"
Name = "some_name"
Machine = "some_name"
grid_resource_name = "condor schedd@mymachine mypool"
Requirements = (CurMatches < 10) && (TARGET.JobUniverse == 9)
Rank = 0.000000
CurrentRank = 0.000000
WantAdRevaluate = True
Activity = "Idle"
State = "Unclaimed"
CurMatches = 0
OpSys = "CondorC"
Arch = "CondorC"
and I am submitting 20 jobs using this description:
universe = grid
Executable = mytest.sh
Output = hello.out
Error = hello.err
Log = hello.log
grid_resource = $$(grid_resource_name)
Requirements = TARGET.grid_resource_name =!= UNDEFINED
+remote_jobuniverse = 5
+remote_requirements = (Arch == "INTEL") && (OpSys == "LINUX")
+remote_ShouldTransferFiles = "YES"
+remote_WhenToTransferOutput = "ON_EXIT"
What I have found is that the CurMatches is never increased after a successful match and that only one job is matched per negotiation cycle (I would expect 10 jobs matched).
Is CurMatches supposed to be increased automatically or should I update the ad in the Collector? Is there a way to enforce more than one match per cycle?Try adding the following to the configuration file of the machine running your negotiator daemon (don't forget to run condor_reconfig afterwards):NEGOTIATOR_MATCHLIST_CACHING = falseIf that fixes the problem, it points out a bug that needs fixing in the negotiator.
Description: Binary data