The Sun Grid Engine 6.2u3 is yet another product update. This means that besides the bug fixes it introduces several new features. But there is another very important difference to the previous releases. The license has changed!
Without a valid Sun Grid Engine license, evaluation use is only permitted for 90 days. If you want to use Grid Engine after that you need to replace the Sun binaries with unsupported courtesy binaries. However the courtesy binaries do not include the new Amazon EC2 adapter and the SGE Inspect modules.
New features in Sun Grid Engine 6.2u3:
Amazon EC2 Adapter
The Service Domain Manager (SDM) adds connectivity to Amazon Elastic Cloud EC2 and the ability to flexibly add execution hosts as needed on demand.
Initial Power Saving Support
A new power saving scheme in SDM enables the creation of a special resource spare pool in which systems can be powered on or off when added or removed from this spare pool.
Service Domain Manager (SDM) Simple Install
It is now possible to install and run an SDM system with only one JVM per (managed or master) host. Previously, the system was using up to three separate JVMs per host. This new feature simplifies installation, configuration and maintenance.
A new Java based Sun Grid Engine Inspect module allows to monitor SGE clusters and the Service Domain Manager (SDM). The similarity to VisualVM or Netbeans is not coincidental.
Exclusive Host Scheduling
Exclusive host scheduling allows users to request that jobs and parallel tasks run exclusively on a host if allowed by an administrator.
Microsoft Windows Vista Display Support
The display_win_gui feature is now fully supported. This feature allows a job to launch a GUI on the currently visible desktop on the Windows host that displays job information. This works only if the job is a native Windows application.
As always, you may test this release in parallel with your old cluster to try out the new features. Optionally,
you may use the upgrade procedure (clone configuration method) to
install SGE 6.2u3, while
keeping all your other cluster configuration settings. See the upgrade video. While the video shows an upgrade from 6.1 to 6.2, it will work the same way for cloning any 6.0u2 or later to 6.2u3.