Policy |
Description |
SHARED |
Tasks from any combination of jobs may utilize available resources |
SINGLEUSER |
Tasks from any jobs owned by the same user may utilize available resources |
SINGLEJOB |
Tasks from a single job may utilize available resources |
SINGLETASK |
A single task from a single job may run on the node |
Node Access polices may be specified via the parameter NODEACCESSPOLICY . The global default may be overridden using QOS flags or on a job-by-job basis using the resource manager extension NACCESSPOLICY . By default, nodes are accessible using the setting of the system wide NODEACCESSPOLICY parameter. However, jobs may override this policy and subsequent jobs are bound to conform to the access policies of all jobs currently running on a given node. For example, if the NODEACCESSPOLICY parameter was set to SHARED, a new job may be launched on an idle node with a job specific access policy of SINGLEUSER. While this job is running, subsequent job tasks may only be launched on this node provided they were submitted by the same user. When all single user jobs have completed on that node, the node can again be used in SHARED mode.