As an alternative, you could create a simple queue (onejobpernode) with 'slots 1'.
-Hugh -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Skylar Thompson Sent: Wednesday, April 02, 2014 11:04 AM To: Tina Friedrich Cc: [email protected] Subject: Re: [gridengine users] array job / node allocation / 'spread' question An exclusive host consumable is the right way to approach the problem. If the task elements might be part of a parallel environment, then you'll want to set the scaling to JOB as well. On Wed, Apr 02, 2014 at 03:39:03PM +0100, Tina Friedrich wrote: > Hello, > > I'm sure this has been asked time and time before, only I can't find > it (search foo failling, somehow). > > What's the best way to run an array job so that each task ends up on > a different node (but they run concurrently)? I don't mind other > jobs running on the nodes at the time, but only want one of mine > (network IO intensive tasks, best use of file system would be lots > of them but spread as far and wide as the can). > > I've thought about introducing a consumable - apart from there's no > node-level consumables at the moment - but am unsure whether that's > the best way to handle this? -- -- Skylar Thompson ([email protected]) -- Genome Sciences Department, System Administrator -- Foege Building S046, (206)-685-7354 -- University of Washington School of Medicine _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
