Hi, It's about seq_no parameter in queue definition.
Assume that you have 2 groups of nodes: node10all and node50all Add this to your queue definition: seq_no 1,[@node10all=50],[@node50all=100] New jobs will start running on nodes node50all Best regards On Wed, Dec 12, 2018 at 8:05 PM Dj Merrill <s...@deej.net> wrote: > I seem to recall reading about this in the past, but I can't > locate the > reference so I'm hoping someone might be able to help. > > We have some older nodes on our SGE system, starting at node50. We > added some new nodes to the system, starting at node10. With a > completely empty Grid (no jobs), we would like newly submitted jobs to > start running on node10 (ignoring for the moment any special resource > requests). Instead, the jobs start on node50, which is the "oldest" > node on the Grid in terms of how long it has been a part of the Grid. > > Is there an easy way to specify a preferred usage order, or will we > have to remove all of the old nodes from the Grid, then re-add them as > new nodes? > > Thanks, > > -Dj > _______________________________________________ > users mailing list > users@gridengine.org > https://gridengine.org/mailman/listinfo/users >
_______________________________________________ users mailing list users@gridengine.org https://gridengine.org/mailman/listinfo/users
