Download as a PDF
Transcript
• Interactive transaction: The co-allocator will not immediately cancel the job, but it looks first at the type of the resources requested by the subjob. If they are required resources, the entire job will be canceled. If they are interactive resources, they will be replaced by others or removed from the RSL script and the updated job request can proceed. The replacement of the resources is done by deleting the corresponding subjob, adding a new subjob, or just modifying the specification for resources in the troubled subjob. If they are optional resources, the co-allocator will ignore them and the job request can proceed without them although it might reduce its performance. Figure 3.1 also shows the two phases of this commit protocol. The resource type of required, interactive, and optional can be specified in RSL attribute labeled subjobStartType with ”strictbarrier”, ”loose-barrier”, and ”no-barrier values”, respectively. DUROC barrier mechanism requires every grid application to invoke a barrier function, namely globus duroc runtime barrier(), that causes every subjob spawned from the application enters a barrier condition. Applications using MPICH-G2 library do not have to invoke the barrier function explicitly since the function has been included already in an MPICH-G2 function called MPI Init(). Likewise, to release the group barrier if all subjobs have entered their barriers, DUROC requires the co-allocator to invoke a barrier-release function called globus duroc barrier release(). We cannot guarantee that a job will complete its execution successfully, even though it is been started up successfully in the allocation period. Configuration Period Every job that has successfully gained its resources in the allocation period will move to the configuration period. At this point, job processes have been created by the local resource manager in all allocated resources. Each process is in a processor (CPU). Upon created, before the execution time, each newly created process needs to configure several variables, e.g.its own rank, the size (number of processes) of the whole job, the number of subjobs in the whole job, the number of processes in a specific subjob. Those processes also need to communicate each other by sending and receiving messages. Direct communication can only be done between two processes in the same subjob or between two processes whose rank ‘0’ in different subjobs. Therefore, if a process wants to communicate with another process in different subjobs must use the ‘rank 0’ processes in their own subjobs as intermediaries. Monitoring/Control Period After configuration period, all job processes over clusters start to execute the application code. The whole job will not complete unless all its processes complete their execution. In the mean time, we can monitor and control the execution of those processes as a collective unit, rather than individual processes. As an example, DUROC provides an API function globus duroc control subjob states() for monitoring states change of every subjob, and function globus duroc job cancel() for canceling the whole job which is an example of control. 3.1.2 How Globus GRAM works The component of the Globus Toolkit to interact with the local scheduler (PBS in this case) in a single cluster is GRAM server. It is composed of a gatekeeper, a job manager, and a reporter, which can be seen in the Figure 3.2. The GRAM gatekeeper is a daemon process situated on every cluster. It works similar to the inetd daemon but it utilizes GSI to authenticate the user. It keeps listening whether there is a job request or client command coming. If so, it receives a job request (in RSL) submitted by a 11