We have two condor pools in our institute. Pool A consists of machines dedicated to calculations only; Pool B consists of staff's desktops. All machines configured with partiotionable slots.
After we configured flocking from Pool A to Pool B I see some strange (at least not desired) behavior of condor.
Pool A has no tasks running. User submits 40 jobs. The pool has 10
8-core computers. Slots are dynamical. Each job requests 2 cores, so all
these jobs exactly fit into the pool. However only 10 first jobs start
running on Pool A, then a portion of jobs immediately flock into Pool B,
and in a minute rest jobs start also on Pool A.
The question is why jobs start to flock when the current pool still have plenty of available resources?
I would expect that flocking starts only after all local resources are exhausted (especially if there are dedicated!)
Thanks a lot for any help how to prevent such an early flocking!