On 29/12/11 19:39, Ciaran Wills wrote:
Another feature which I couldn't figure out how to achieve is per-host dependencies (particularly in array dependencies) - if one task is going to generate a load of data for another task to consume then I could write it all to the local tmp drive if I know the dependent task will run on the same host rather than pushing it across the network. Instead I just wrap those tasks up into a single task submission which is fine for single dependencies but it would be nice to have something more flexible.
How would you want to deal with a situation where task A finished, and task B is about to run on the same host, but then the host is taken offline. Would you expect to reschedule task A (which considers itself finished) to run again on another host, or just leave task B hanging and unable to run?
I would probably prefer to do what you're doing in this case and run both tasks as a single task - that way, if something is taken offline, the whole thing can run on another host from the start...
Hugh Macdonald *n**vizible**-- **VISUAL EFFECTS* www.nvizible.com <http://www.nvizible.com/>
_______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
