The node startup or node build cannot include all the steps because the purpose of the grid is regression testing of new builds of a software tool.
The execd node needs to locally install the new build. I could perhaps use a single network location that all execd hosts use for their installation, but, in my experience, performance of network file systems is poor under Cygwin. Simon On Mon, Nov 6, 2017 at 3:08 PM, MacMullan IV, Hugh <[email protected]> wrote: > You could put that code in the exec startup script, above the line that > starts execd, and error out if that part doesn’t complete successfully. > > Seems weird, though. Shouldn’t the node build include all necessary bits to > set up your execd nodes to ‘run jobs’? Are these on your Cygwin cluster? > Perhaps you could tell us all a bit more about the project in general, so > that we can think further ahead than your single-answer questions? > > -Hugh > > On Nov 6, 2017, at 16:32, Simon Matthews <[email protected]> wrote: > > I need to run a job on every execd host that must be run before the > main batch of jobs are run. > > I could submit a "setup" job on each specific execd host and make all > the subsequent jobs dependent on the list of "setup" jobs, but, if one > setup job gets hung up, all the subsequent jobs will wait, even though > they could be executed on other execd hosts. > > Is there some way to prevent jobs from running on a particular execd > hosts until after a "setup" job has run on that host? Or, to put it > another way, the setup job enables other jobs to run on the execd > host? > > Simon > _______________________________________________ > users mailing list > [email protected] > https://gridengine.org/mailman/listinfo/users _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
