Am 21.06.2012 um 15:36 schrieb Joe Borġ: > Yep, the SGE manual states: "Slots. The number of jobs that are allowed to > run concurrently in the queue. Slots are also referred to as job slots."
Well, many phrases in the manual which originate from the former SGE5.3 only refer to a queue, as one queue was running on one and only one exechost at that time (yes, you needed many queues at that time in a large cluster). With SGE6.0 the paradigm was changed and a queue definition will have a queue instance on each of the specified machines in the hostlist and each entry refers to the setting inside a queue instance. In addition, the difference between "slot" and "job" is sometimes blurred. As long as you have only serial jobs, they can be used interchangeable. But not for parallel jobs, where a job will occupy more than just one slot. -- Reuti > So you can see where confusion comes from. I'll write a load sensor. Thanks > for the help. > > > Regards, > Joseph David Borġ > http://www.jdborg.com > > > On 21 June 2012 12:48, Reuti <re...@staff.uni-marburg.de> wrote: > Am 21.06.2012 um 11:35 schrieb Joe Borġ: > > > It's not just SGE that run on these, they are designed to fail over. It's > > critical stuff on them, so not really a waste. > > > > Why when I set "Slots" to 1 can a job start on each node? Is this the way > > it's mean to work? > > Yes, it's the slot count per queue instance - i.e. per exechost in the > defined hostlist. > > But using a consumable complex might also not work, as it's still marked as > used in SGE's internal bookkeeping I would say. A vanishing node shouldn't > change the complex consumption for already running jobs. > > Therefore the idea with the load sensor. > > -- Reuti > > > > > > Regards, > > Joseph David Borġ > > http://www.jdborg.com > > > > > > On 20 June 2012 17:41, Reuti <re...@staff.uni-marburg.de> wrote: > > Am 20.06.2012 um 18:22 schrieb Joe Borġ: > > > > > I've got a queue with two hosts in. I'd like to set this up so host2 is > > > only used when host1 goes into state "au". Currently I'm using > > > consumable resources to limit one job at a time, but this doesn't seem > > > the best way. > > > > You mean host2 is idle under normal circumstance - isn't it a waste of > > resources when the machine is running anyway? You could use a load sensor > > on host2 which checks the availability of host1 and enables/disables the > > queue instance on host2.(the load sensor could change a boolean complex). > > > > -- Reuti > > > > > > > Any suggestions? > > > > > > > > > Regards, > > > Joseph David Borġ > > > http://www.jdborg.com > > > _______________________________________________ > > > users mailing list > > > users@gridengine.org > > > https://gridengine.org/mailman/listinfo/users > > > > > > _______________________________________________ users mailing list users@gridengine.org https://gridengine.org/mailman/listinfo/users
