Hi all, is there actually a way to peak into the matchmaking process between a node and the negotiator? Thing is, that I have a few test nodes, which have all the same configs and mostly similar hardware. However, jobs targeted at these nodes start only on one of them and that sometimes with quite some delay. In some nodes' StartLog I found for some of these jobs(?) (assuming correlation in time), that while the Negotiator scheduled a job to a slot the node itself rejected the job (although nothing else run and all resources were available as far as I saw...) On the other hand, for some nodes/times their StartLog is effectively empty without signs, that the node was actually considered during matchmaking? (-avail/-long stats looked OK to me skimming over the ads) So, is there a reasonable way to peak into the Negotiators decision making why or why not to consider a node for a given job? As far as I see with condor_status one can get only a node/slot's offers, or? Cheers and thanks for ideas, Thomas
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature