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

[HTCondor-users] Some jobs of batch stays in idle state for longer time



Hello Experts,

We have seen issues where some jobs of the batch stays in idle status, We are using scheduler level splitting. 

Let's say a batch of 300 jobs is submitted, cores are available to do match making of let's say 280-290 jobs, negotiator do the match making of 280 jobs, 20 jobs stay in idle status even when the cores are available in the cluster but if we submit new batch it's getting scheduled immediately. 

Is HTcondor also considering the time spent by the job in the queue before scheduling, maybe it's considering new jobs more quickly? 
Time spent by jobs in queue sometimes goes upto 45 mins despite having cores available in cluster.  
Master logs only show no match found for 20 idle jobs but it can find resources for new jobs. 

Thanks & Regards,
Vikrant Aggarwal