Planning the HA for Oracle Grid Engine Installation and Configuration

This section contains the information that you need to plan your HA for Oracle Grid Engine installation and configuration.

Note - Before you begin, consult your Oracle Grid Engine documentation for configuration restrictions and requirements that are not imposed by Oracle Solaris Cluster software.

Configuration Restrictions

The configuration restrictions in the subsections that follow apply only to HA for Oracle Grid Engine.

Caution - Your data service configuration might not be supported if you do not observe these restrictions.

Oracle Grid Engine Shadow Daemon

Do not use the Oracle Grid Engine shadow daemon. The Oracle Grid Engine shadow daemon provides an optional mechanism for recovery from failures. This mechanism interferes with the automatic fault recovery that Oracle Solaris Cluster provides.

Oracle Grid Engine Berkley DB spooling server

Do not choose the option to use a Berkley DB spooling server. Either choose the Classic spooling method or the local Berkley DB spooling method. Currently it is not possible to configure the Berkley DB spooling server in a highly available way within the Oracle Solaris Cluster framework.

Start at Boot Option

Do not choose the start at boot option when installing Oracle Grid Engine. To ensure that HA for Oracle Grid Engine can provide fault monitoring and automatic fault recovery, Oracle Grid Engine must be started only by Oracle Solaris Cluster.

Configuration Requirements

The configuration requirements in this section apply only to HA for Oracle Grid Engine.

Caution - If your data service configuration does not conform to these requirements, the data service configuration might not be supported.

Oracle Grid Engine Software Version Requirements

Use Oracle Grid Engine version 6.0 or 6.1. Make sure to apply the most recent available Patches to the Oracle Grid Engine software.

Operating System for the Oracle Grid Engine Management Tier

The Oracle Grid Engine management tier must run on Oracle Solaris Cluster nodes. Because Oracle Solaris Cluster runs only on the Solaris Operating System, the Oracle Grid Engine management tier must also run on the Solaris Operating System. However, Oracle Grid Engine supports other operating systems. Therefore, this requirement applies only to the management tier, not to individual execution nodes in the grid.

Memory Requirements

Ensure that enough free memory is available on the cluster nodes where you plan to run the Oracle 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.

Disk Space Requirements

Ensure that you have enough disk space in the Oracle 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 Oracle 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 Oracle Grid Engine software on the local disk of a node, 15 Mbytes of disk space are additionally required for the binary files.

HA for Oracle Grid Engine Configuration Requirements

Configure HA for Oracle Grid Engine as a failover data service. You cannot configure HA for Oracle Grid Engine as a scalable data service. For more information, see:

Note - If you are using the Solaris 10 OS, install and configure this data service to run only in the global zone. At publication of this document, this data service is not supported in non-global zones. For updated information about supported configurations of this data service, contact your Oracle service representative.

NFS Configuration for the Oracle Grid Engine File System

The Oracle 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 Oracle Grid Engine administrative services,

You must use NFS to export the Oracle 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 Oracle Solaris Cluster HA for NFS data service. For more information about this data service, see Oracle Solaris Cluster Data Service for Network File System (NFS) Guide.

Oracle Solaris Cluster HA for NFS Configuration Requirements

Configure the resources for the Oracle Grid Engine management tier in the same resource group as the resource for NFS. For more information, see Configuring Oracle Solaris Cluster HA for NFS for Use With HA for Oracle Grid Engine.

Dependencies Between Oracle Grid Engine Components

The dependencies between Oracle Grid Engine components are shown in the following table.

Table 1-3 Dependencies Between Oracle Grid Engine Components

Oracle Grid Engine Component	Dependency
Oracle Grid Engine queue master daemon (`sge_qmaster`)	`SUNW.HAStoragePlus` resource
Oracle Grid Enginescheduling daemon (`sge_schedd`)	Oracle Grid Engine queue master daemon (`sge_qmaster`) resource

These dependencies are set when you register and configure HA for Oracle Grid Engine. For more information, see Registering and Configuring HA for Oracle Grid Engine.

Configuration Considerations

The configuration considerations in the subsections that follow affect the installation and configuration of HA for Oracle Grid Engine.

Location of the Oracle Grid Engine Binary Files

You can install Oracle Grid Engine on one of the following locations:

A highly available local file system
The cluster file system

For the advantages and disadvantages of placing the Oracle Grid Engine binary files on a highly available local file system and the cluster file system, see Configuration Guidelines for Oracle Solaris Cluster Data Services in Oracle Solaris Cluster Data Services Planning and Administration Guide.

Tip - To enable the type of file system to be identified from the mount point, use a prefix that indicates the type of file system as follows:

For mount points on a highly available local file system, use the /local prefix.
For mount points on the cluster file system, use the /global prefix.

File Systems for Spool Directories and Binary Files

The optimum distribution of spool directories and binary files among file systems depends on the grid configuration. See the following table.

Grid Configuration	File System Configuration
The execution tier contains fewer than 200 hosts.	Use a single shared NFS file system under the root of the Oracle Grid Engine file system for the spool directories and binary files.
The execution tier contains about 200 hosts, or the applications are disk intensive.	Use a separate area on an NFS file system for the spool directories.
The execution tier contains more than 200 hosts, or NFS performance is likely to be a problem.	See the Oracle Grid Engine documentation for alternate grid configurations.

Configuration Planning Questions

Use the questions in this section to plan the installation and configuration of HA for Oracle Grid Engine. Write the answers to these questions in the space that is provided on the data service worksheets in Configuration Worksheets in Oracle Solaris Cluster Data Services Planning and Administration Guide.

Which resource group will you use for the following resources:
- Logical host name resource
- HAStoragePlus resource
- NFS resource
- Oracle Grid Engine application resources
Use the answer to this question when you perform the following procedures:
What is the logical host name for the Oracle Grid Engine resource? Clients access the data service through this logical host name.

Use the answer to this question when you perform the procedure How to Enable Oracle Grid Engine to Run in a Cluster.
Which resources will you use for the components of Oracle Grid Engine?

You require one resource for each component in the following list:
- Queue master daemon
- Scheduling daemon
Use the answer to this question when you perform the procedure Specifying Configuration Parameters for HA for Oracle Grid Engine Resources.
Where will the system configuration files reside?

See Configuration Guidelines for Oracle Solaris Cluster Data Services in Oracle Solaris Cluster Data Services Planning and Administration Guide for the advantages and disadvantages of using the local file system instead of the cluster file system.

Skip Navigation Links
Exit Print View
	Oracle Solaris Cluster Data Service for Oracle Grid Engine Guide