Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Data Service for Oracle Grid Engine Guide |
1. Installing and Configuring HA for Oracle Grid Engine
HA for Oracle Grid Engine Overview
Overview of Installing and Configuring HA for Oracle Grid Engine
Planning the HA for Oracle Grid Engine Installation and Configuration
Oracle Grid Engine Shadow Daemon
Oracle Grid Engine Berkley DB spooling server
Oracle Grid Engine Software Version Requirements
Operating System for the Oracle Grid Engine Management Tier
HA for Oracle Grid Engine Configuration Requirements
NFS Configuration for the Oracle Grid Engine File System
Oracle Solaris Cluster HA for NFS Configuration Requirements
Dependencies Between Oracle Grid Engine Components
Location of the Oracle Grid Engine Binary Files
File Systems for Spool Directories and Binary Files
Configuration Planning Questions
Installing and Configuring Oracle Grid Engine
How to Install and Configure Oracle Grid Engine
How to Enable Oracle Grid Engine to Run in a Cluster
Verifying the Installation and Configuration of Oracle Grid Engine
How to Verify the Installation and Configuration of Oracle Grid Engine
Installing the HA for Oracle Grid Engine Packages
How to Install the HA for Oracle Grid Engine Packages
Configuring the HAStoragePlus Resource Type to Work With HA for Oracle Grid Engine
How to Register and Configure an HAStoragePlus Resource
Configuring Oracle Solaris Cluster HA for NFS for Use With HA for Oracle Grid Engine
How to Configure Oracle Solaris Cluster HA for NFS for Use With HA for Oracle Grid Engine
Registering and Configuring HA for Oracle Grid Engine
Specifying Configuration Parameters for HA for Oracle Grid Engine Resources
How to Create and Enable HA for Oracle Grid Engine Resources
Setting HA for Oracle Grid Engine Extension Properties
Verifying the HA for Oracle Grid Engine Installation and Configuration
How to Verify the HA for Oracle Grid Engine Installation and Configuration
Tuning the HA for Oracle Grid Engine Fault Monitors
Debugging HA for Oracle Grid Engine
How to Activate Debugging for HA for Oracle Grid Engine
A. Files for Configuring and Removing HA for Oracle Grid Engine Resources
Preparing the nodes and disks modifies the configuration of the operating system to enable HA for Oracle Grid Engine to eliminate single points of failure in an Oracle Grid Engine system.
Before you begin, ensure that the requirements in the following sections are met:
Either select an existing user account other than root for the grid administration, or create an account specifically for grid administration.
# mkdir sge-root-dir
Note - The sge-root-dir must reside in the cluster filesystem. Refer to Configuring the HAStoragePlus Resource Type to Work With HA for Oracle Grid Engine for more details.
# chown sge-admin sge-root-dir
# chmod 755 sge-root-dir
Choose an unused port number below 1024. The sge_qmaster and sge_execd services are to be provided through Transmission Control Protocol (TCP).
To specify the port number and protocol, add the following line to the /etc/services file.
sge_qmaster port-no/tcp sge_execd port-no/tcp
The install_qmaster script uses these files when you install Oracle Grid Engine. Create a separate file for each type of host in the grid:
Execution hosts
Administrative hosts
Submit hosts
Example 1-1 Preparing the Nodes and Disks for the Installation of Oracle Grid Engine
This example shows how to prepare the nodes and disks for an Oracle Grid Engine installation that is to be configured as follows:
The root of Oracle Grid Engine file system is the /global/gridmaster directory. This directory resides in the cluster file system.
The account for grid administration is named sgeadmin.
The sge_qmaster service is to be provided through port 536 and TCP.
The sge_execd service is to be provided through port 537 and TCP.
The sequence of operations for preparing the nodes and disks for the installation of Oracle Grid Engine is as follows:
To create the /global/gridmaster directory for the root of Oracle Grid Engine file system, the following command is run:
# mkdir /global/gridmaster
To change the owner of the /global/gridmaster directory to the sgeadmin user, the following command is run:
# chown sgeadmin /global/gridmaster
To set the mode of the /global/gridmaster directory to drwxr-xr-x, the following command is run:
# chmod 755 /global/gridmaster
To specify that the sge_qmaster service is to be provided through port 536 and TCP, and that the sge_execd service is to be provided through port 537 and TCP, the following line is added to the /etc/services file:
sge_qmaster 536/tcp sge_execd 537/tcp