| Moab Workload Manager® for Grids |
17.7 Workload Submission and Control
17.7.1 Controlling Peer Workload Information
By default, a peer is only responsible for workload that is submitted via that particular peer. This means that when a source peer communicates with destination peers it only receives information about workload it sent to those destination peers. If desired, the destination peers can send information about all of its workload: both jobs originating locally and remotely. This is called local workload exporting. This may help simplify administration of different clusters by centralizing monitoring and management of jobs at one peer and avoids forcing each peer to the type SLAVE.
To implement local workload exporting, use the LOCALWORKLOADEXPORT resource manager flag. For example:
The preceding example shows the configuration on a destination peer (ClusterB) that exports its local and remote workload to the source peer (ClusterA).
NOTE: The LOCALWORKLOADEXPORT flag or SLAVE mode will not work if the destination peer is in GRID mode.
NOTE: The LOCALWORKLOADEXPORT flag is only operational when used with the CLIENT flag in a destination peer's configuration.
17.7.2 Determining Resource Availability
By default, Moab identifies best destination resources using local information imported from remote peers. This behavior can be changed by setting the RESOURCEAVAILABILITYQUERYMETHOD attribute on the associated resource manager using RMCFG. If remote peers are queried, their ability to learn and improve start time estimate accuracy over time can be enabled by setting the ENABLESTARTESTIMATESTATS parameter on each destination peer.
See Also