On 5 April 2013 09:16, Andreas Haupt <[email protected]> wrote: > Hi Reuti, > > On Fri, 2013-04-05 at 09:58 +0200, Reuti wrote: > > Am 05.04.2013 um 00:25 schrieb Adam Brenner: > > > Howdy All, > > > > > > Running GE 8.1.2. I have setup a consumable resource on our cluster > > > (of type memory), and it works great. How would I be able to grab a > > > value of that consumable resource via a prolog/epilog script? Example: > > > qrsh -l my_consumable_resource_of_type_memory=88G > > > then in a prolog/epilog script get the value of 88G > > > > > > I have taken a look the $SGE_JOB_SPOOL_DIR both 'config' and > > > 'environment' files does not contain any reference to my consumable > > > resource (strange, right?) > > > > it's necessary to use `qstat -j $JOB_ID` and `grep` the relevant > information inside prolog/epilog. Even better and easier to parse would be > `qstat -r` for the granted resources (like name of the granted PE). > Unfortunately the latter can't be limited to the output of a single job. > > Unfortunately, yet. But on large clusters with high job throughput this > can put a very high load on the SGE master. A general SGE enhancement > would be very helpful here! > > We have a different approach to solve this problem: in the server-side > jsv the value is put into the job's environment via > jsv_add_env("ENV_NAME", $value). This value can then be read by the > prolog script from the "$SGE_JOB_SPOOL_DIR/environment" file. > > We do something similar here. If one wanted to skip all that tedious mucking about with JSVs one could set MONITOR=1 in the scheduler's params and pull the data out of the schedule file. Of course that assumes the file server where the schedule file is stored can handle the load.
William > Cheers, > Andreas > -- > | Andreas Haupt | E-Mail: [email protected] > | DESY Zeuthen | WWW: http://www-zeuthen.desy.de/~ahaupt > | Platanenallee 6 | Phone: +49/33762/7-7359 > | D-15738 Zeuthen | Fax: +49/33762/7-7216 > > > _______________________________________________ > users mailing list > [email protected] > https://gridengine.org/mailman/listinfo/users > > >
_______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
