The configuration requirements in this section apply only to Sun Cluster HA for Sun Grid Engine.
If your data service configuration does not conform to these requirements, the data service configuration might not be supported.
Use Sun Grid Engine version 6.0. Make sure to apply the most recent available Patches to the Sun Grid Engine software.
Although Sun Grid Engine version 5.3 has reached its end of life, Sun Cluster HA for Sun Grid Engine still supports this version. If you are using Sun Grid Engine version 5.3, consider upgrading to Sun Grid Engine version 6.0.
The instructions in this book apply only to Sun Grid Engine version 6.0. For information about how to install and configure Sun Cluster HA for Sun Grid Engine with Sun Grid Engine version 5.3, see Sun Cluster Data Service for Sun Grid Engine Guide for Solaris OS for Sun Cluster 3.1 9/04.
Since Sun Cluster 3.1 9/04 was released, keywords in the sge_config file are changed as follows:
RG is changed to MASTERRG.
LH is changed to MASTERLH.
PORT is changed to MASTERPORT.
SGE_VER is introduced.
For an explanation of these keywords, read the comments in the sge_config file.
The Sun Grid Engine management tier must run on Sun Cluster nodes. Because Sun Cluster runs only on the Solaris Operating System, the Sun Grid Engine management tier must also run on the Solaris Operating System. However, Sun Grid Engine supports other operating systems. Therefore, this requirement applies only to the management tier, not to individual execution nodes in the grid.
Ensure that enough free memory is available on the cluster nodes where you plan to run the Sun Grid Engine master.
The amount of free memory that is required on each cluster node depends on the number of jobs that are running on the grid. For example:
If 100 jobs are running, 10 Mbytes of free memory are required.
If 10,000 jobs are running, 1 Gbyte of free memory is required.
Ensure that you have enough disk space in the Sun Grid Engine file system and on the local disk of each node.
The disk space requirements for each type of file or directory in the Sun Grid Engine file system are listed in the following table.
File Type or Directory Type |
Required Disk Space |
---|---|
Binary files |
15 Mbytes for each architecture |
Spool directories |
30–200 Mbytes |
Installation tar file |
40 Mbytes |
On the local disk of each node, 10–20 Mbytes of disk space are required. If you are installing the Sun Grid Engine software on the local disk of a node, 15 Mbytes of disk space are additionally required for the binary files.
Configure Sun Cluster HA for Sun Grid Engine as a failover data service. You cannot configure Sun Cluster HA for Sun Grid Engine as a scalable data service. For more information, see:
The Sun Grid Engine file system must reside on a multihost disk. This disk must be available to the other nodes in the cluster that will be used for the Sun Grid Engine administrative services,
You must use NFS to export the Sun Grid Engine file system to the noncluster nodes. The NFS server that exports this file system must also be protected against failure. To protect the NFS server against failure, use the Sun Cluster HA for NFS data service. For more information about this data service, see Sun Cluster Data Service for NFS Guide for Solaris OS.
Configure the resources for the Sun Grid Engine management tier in the same resource group as the resource for NFS. For more information, see Configuring Sun Cluster HA for NFS for Use With Sun Cluster HA for Sun Grid Engine.
The dependencies between Sun Grid Engine components are shown in the following table.
Table 3 Dependencies Between Sun Grid Engine Components
Sun Grid Engine Component |
Dependency |
---|---|
Sun Grid Engine queue master daemon (sge_qmaster) |
SUNW.HAStoragePlus resource |
Sun Grid Enginescheduling daemon (sge_schedd) |
Sun Grid Engine queue master daemon (sge_qmaster) resource |
These dependencies are set when you register and configure Sun Cluster HA for Sun Grid Engine. For more information, see Registering and Configuring Sun Cluster HA for Sun Grid Engine.