You can run the Grid Engine testsuite, but the setup process will be harder than a fresh SGE compile.
But, you can just run the loadcheck binary to check the hardware stats reported by SGE - both loadcheck & the execution daemon use the same set of internal libraries... so if loadcheck runs, then the execd should be fine. Then setup a 1-node test cluster and test a few basic jobs run by your cluster - if they run fine & the resource usage is reported correctly, then I am pretty sure (99+%) that SGE runs fine. Of course one can never tell unless it is run in real production... and I have encountered sites that have 4 idential clusters - 1 for development, 1 for test/UAT, 1 for production, and 1 for failover/backup. (The site is a bank and the results calculated are used for multi billion dollar trades). If your SGE is that critical then you may want to consider these kind of setups. Otherwise, I would say it is really not worth the trouble to fully test SGE after an OS upgrade. Rayson On Thu, Dec 1, 2011 at 12:35 PM, Alan McKay <[email protected]> wrote: >> Note that all those issues are fixed in later versions of SGE, but if >> you are not doing any of the above upgrades, then SGE 6.2u5 should run >> happily. > > Is there any sort of self-test that can be run to check it over after > an OS upgrade? > > > > > -- > “Don't eat anything you've ever seen advertised on TV” > - Michael Pollan, author of "In Defense of Food" > > _______________________________________________ > users mailing list > [email protected] > https://gridengine.org/mailman/listinfo/users _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
