LinuxHPC.org/Cluster Builder 1.3
Batch System
Batch System
By LinuxHPC.org and Cluster Resources
| Batch System |
|
Batch systems are a collection of computers and other resources (networks, storage systems, license servers, etc.) with the idea that the whole is greater than the sum of the parts. Some batch systems consist of just a handful of machines running single-processor jobs, minimally managed by the users themselves. Other systems have thousands and thousands of machines executing users’ jobs simultaneously while tracking software licenses and access to hardware equipment and storage systems.
Pooling resources in a batch system typically reduces technical administration of resources and a uniform view to users. Once configured properly, batch systems abstract away many of the details involved with running and managing jobs, allowing higher utilization of resources. For example, users typically only need to specify the minimal constraints of a job and do not need to know the individual machine names of each host that they are running on. With this uniform abstracted view, batch systems can execute thousands and thousands of jobs simultaneously.
Batch systems are comprised of four different types components:
- Master Node
- Submit/Interactive Nodes
- Compute Nodes
- Resources
A batch system will have a master node where a management application is running. Depending on the needs of the systems, a master node may be dedicated to this task or may fulfill the roles of other components as well.
Submit/Interactive Nodes
Submit or interactive nodes provide an entry point to the system for users to be able to manage their workload. For these nodes, users are able to submit and track their jobs. Additionally, some sites have one or more nodes reserved for interactive use, such as testing and troubleshooting environment problems. These nodes will have client commands available.
Compute Nodes
Compute Nodes are the work horses of the system. Their role is to execute submitted jobs. On each compute node, an application will be running to start, kill and manage submitted jobs. It communicates with the management application on the master node. Depending on the needs of the systems, a compute node may double as the master node (or more).
Resources
Some systems are organized for the express purpose of managing a collection of resources beyond compute nodes. Resources can include high-speed networks, storage systems, license managers, etc. Availability of these resources is limited and need to be managed intelligently to promote fairness and increased utilization.
The information used to create this article was found in the TORQUE Resource Manager Admin Manual provided by Cluster Resources, Inc.