Sun Microsystems
Products & Services
 
Support & Training
 
 

Previous Previous     Contents     Index     Next Next

Execution Hosts

Execution hosts run the jobs that users submit to the grid engine system. An execution host must first be set up as an administration host. You run an installation script on each execution host.

Group IDs

You need to provide a range of IDs that will be assigned dynamically for jobs. The range must be big enough to provide enough numbers for the maximum number of grid engine system jobs running at a single moment on a single host.

A group ID is assigned to each grid engine system job to monitor the resource utilization of the job. Each job will be assigned a unique ID during the time it is running. For example, a range of 20000-20100 allows 100 jobs to run concurrently on a single host. You can change the group ID range for your cluster configuration at any time, but the values in the UNIX group ID range must be unused on your system.

Administration Hosts

Operators and managers of the grid engine system use administration hosts to perform administrative tasks such as reconfiguring queues or adding grid engine system users.

The master host installation script automatically makes the master host an administration host. During the master host installation process, you can add other administration hosts. You can also manually add administration hosts on the master host at any time after installation.

Submit Hosts

Jobs can be submitted and controlled from submit hosts. The master host installation script automatically makes the master host a submit host.

Cluster Queues

The installation procedure creates a default cluster queue structure, which is suitable for getting acquainted with the system. The default queue can be removed after installation.


Note - No matter what directory is used for the installation of the software, the administrator can change most settings that were created by the installation procedure. This change can be made while the system is running.


There are several factors you need to consider when determining a queue structure.

  • Whether you need cluster queues for sequential, interactive, parallel, and other job types

  • Which queue instances to put on which execution hosts

  • How many job slots are needed in each queue

For more detailed information on administering cluster queues, see "Configuring Queues" in N1 Grid Engine 6 Administration Guide.

Scheduler Profiles

You can choose from three scheduler profiles during the installation process: normal, high, and max. You can use these predefined profiles as a starting point for grid engine tuning.

Using these profiles, you can optimize the scheduler for one or more of the following:

  • The amount of information about a scheduling run

  • The load adjustment during a scheduling run

  • Interval scheduling (the default) or immediate scheduling

You can choose from three scheduler profiles:

  • normal-- This profile uses load adaptation, and interval scheduling, and reports all the information that the scheduler gathers during the dispatch cycle. This profile is the starting point for most grids. Use this profile if your highest priority is gathering and reporting information about a scheduling run.

  • high-- This profile is more appropriate for a large cluster, where throughput is more important than gathering and reporting all the information from the scheduler. This profile also uses interval scheduling. Use this profile if you want to get better performance at the cost of getting less information about your scheduling runs.

  • max-- This profile disables all information gathering and reporting, enables immediate scheduling, and disables load adaptation. Immediate scheduling is very useful for sites with high throughput and very short running jobs. The advantage of immediate scheduling decreases as run time of the jobs increases. This profile can be used in clusters of any size where only throughput is important and everything else is a lower priority.

For more information on how to configure scheduling, see "Administering the Scheduler" in N1 Grid Engine 6 Administration Guide.

Installation Method

Several methods are available for installing the grid engine software:

  • Interactive

  • Interactive, with increased security

  • Automated, using the inst_sge script and a configuration file

  • Upgrade

To decide which installation method you should use, consider the following factors.

Check the Other Installation Issues Appendix

If you are installing N1GE on a Linux system or on a system with IPMP, see the Other Installation Issues appendix for some important information.

Loading the Distribution Files On a Workstation

Grid Engine is distributed on CD-ROM, and through electronic download. For information on how to access CD-ROMs, ask your system administrator or refer to your local system documentation. The CD-ROM distribution contains a directory named N1_Grid_Engine_6u4. The product distribution is in this directory, in both tar.gz format and the pkgadd format. The pkgadd format is provided for the Solaris™ Operating System (Solaris OS). For all supported operating systems, the software is distributed in tar.gz format.

Previous Previous     Contents     Index     Next Next