AFAICT, the perl jsv threads stay running for performance reasons as was talked about way back when...
Having values updateable by adjusting a parameters file and having the threads update it's own parameters by checking every 3 minutes or so for a change may work nicer than having to kill them off so that they restart again...kinda of an incomplete integration.... I'll look into a possible solution for this as it should be relatively easy... esp on verify...we could check a timer quick to see if the min time to check has expired...and if so, check the file for parameter diffs and set them if so - thereby eliminating the need to restart the jsv perl threads....On a large cluster, you can have say 4-8 threads running.....depending on the bootstrap config file values. -Ed -----Original Message----- From: Reuti [mailto:[email protected]] Sent: Wednesday, May 29, 2013 04:58 PM To: 'Ed Lauzier' Cc: [email protected] Subject: Re: [gridengine users] JSV - parameter updates and restart methodologies Am 29.05.2013 um 22:42 schrieb Ed Lauzier:> I've been running perl JSV server side scripts and they run fine.> When they need updating is when we have to do things> alittle crude at the moment. ( kill them and have the scheduler> restart them on the next job submission...)You mean they are running in a loop like a load sensor instead of being started for each job submission?-- Reuti> Would it be possible to set a parameter update interval so that > all we would have to do is edit a parameters file and the parameters needed> for the JSV to set runtime limits for example would update itself....> > Has this already been done? If so, please let me know the methodology> used in implementing such a solution.> > Thanks,> > Ed Lauzier> > _______________________________________________> users mailing list> [email protected]> https://gridengine.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
