On Thu, Mar 09, 2017 at 07:29:25PM +0100, Roberto Nunnari wrote: > I don't mean move from node to node.. by moving I mean that something > happens in the scheduler.. that the scheduler reserves a slot for the > pending job requesting reservation.. in the schedule file, I see only lines > with the word RESERVING.. and never something like RESERVED.. or little > changes that tell me that something is changing.. I always see lines like > these: > 3653372:1:RESERVING:1489043424:660:P:smp:slots:32.000000 > 3653372:1:RESERVING:1489043424:660:Q:long.q@node19.cluster:slots:32.000000 > I believe that if the scheduler reserves a slot, something in these lines > should change..
Nope. RESERVING is what the schedule file says when the scheduler reserves a resource. The file is describing what the scheduler is doing not the state of the resource. One quirk is that the scheduler reconsiders where the reservation goes with each scheduling cycle. The reservation just prevents jobs from starting that would conflict with the reservation this scheduling cycle. This means that the same resources should have the same predicted availability next scheduling cycle.. As long as the number in the 4th field isn't continually increase your job should eventually get the resources marked as RESERVING. One quirk is that if you heavily weight a per user functional share policy(like we do at UCL) then small jobs from a user backfilling can deprive large jobs from that same user of the priority needed to hold onto a reservation. The workaround for this is to educate said users to have their small jobs wait for (depend on) the large job to run. If you use functional share based on somethng other than users have fun convincing said users to co-ordinate. William
signature.asc
Description: Digital signature
_______________________________________________ users mailing list users@gridengine.org https://gridengine.org/mailman/listinfo/users
