mschedctl | (Moab Scheduler Control) |
Synopsis
mschedctl -A '<MESSAGE>' mschedctl -c message messagestring [-o type:val] mschedctl -c trigger triggerid -o type:val mschedctl -d trigger triggerid mschedctl -d vpc:vpcid mschedctl -d message:index mschedctl -f {all|estimates|fairshare|usage} mschedctl -k mschedctl -l {config|message|trigger|trans|vpc|vpcprofile} [--flags=verbose] [--xml] mschedctl -L [LOGLEVEL] mschedctl -m config string [-e] [--flags=persistent] mschedctl -m trigger triggerid attr=val[,attr=val...] mschedctl -m vpc vpcid attr=val[,attr=val...] mschedctl -n mschedctl -p mschedctl -r [resumetime] mschedctl -R mschedctl -s [STOPITERATION] mschedctl -S [STEPITERATION]
Overview
The mschedctl command controls various aspects of scheduling behavior. It is used to manage scheduling activity, shutdown the scheduler, and create resource trace files. It can also evaluate, modify, and create parameters, triggers, and messages.With many flags, the '--msg=<MSG>' option can be specified to annotate the action in the event log. |
Format
-A — ANNOTATE | |||||
Format: | <STRING> | ||||
Default: | --- | ||||
Description: | Report the specified parameter modification to the event log and annotate it with the specified message. | ||||
Example: | > mschedctl --flags=pers -A 'increase logging' -m 'LOGLEVEL 6' |
||||
-c — CREATE | |||||
Format: | One of:
|
||||
Default: | --- | ||||
Description: | Create a message or trigger and attach it to the specified object, or create a Virtual Private Cluster (VPC). To create a trigger on a default object, use the Moab configuration file (moab.cfg) rather than the mschedctl command. | ||||
Example: | mschedctl -c message tell the admin to be nice mschedctl -c trigger EType=start,AType=exec,Action="/tmp/email $OWNER $TIME" -o rsv:system.1
mschedctl -c vpc -a resources=6,7,8 -a profile=packageA
|
||||
-d — DESTROY | |||||
Format: | One of:
|
||||
Default: | --- | ||||
Description: | Delete a trigger, message, or VPC. | ||||
Example: | mschedctl -d trigger 3 mschedctl -d message:5 mschedctl -d vpc:vpc.5 mschedctl -d vpc:ALL |
||||
-f — FLUSH | |||||
Format: | {all|estimates|fairshare|usage} | ||||
Default: | --- | ||||
Description: | Flush (clear out) specified statistics | ||||
Example: | mschedctl -f usage |
||||
-k — KILL | |||||
Format: | --- | ||||
Default: | --- | ||||
Description: | Stop scheduling and exit the scheduler | ||||
Example: | mschedctl -k
Kill the scheduler. |
||||
-l — LIST | |||||
Format: | {config | gres | message | trans | trigger | vpc | vpcprofile} [--flags=verbose] [--xml]
|
||||
Default: | config | ||||
Description: | List the generic resources, scheduler configuration, system messages, triggers, transactions, virtual private clusters or VPC profiles. | ||||
Example: | mschedctl -l config mschedctl -l gres mschedctl -l trans 1 mschedctl -l trigger mschedctl -l vpc mschedctl -l vpc:vpc.1 |
||||
-L — LOG | |||||
Format: | <INTEGER> | ||||
Default: | 7 | ||||
Description: | Create a temporary log file with the specified loglevel. | ||||
Example: | > mschedctl -L 7 |
||||
-m — MODIFY | |||||
Format: | One of:
|
||||
Default: | --- | ||||
Description: | Modify a system parameter, trigger, or VPC. | ||||
Example: | > mschedctl -m config LOGLEVEL 9 > mschedctl -m trigger:2 AType=exec,Offset=200,OID=system.1 > mschedctl -m vpc:packageA.1 variables=blue=dog > mschedctl -m vpc:vpc.10 user=craig vpc USER set to craig |
||||
-n — NODE TRACE | |||||
Format: | --- | ||||
Default: | --- | ||||
Description: | Output a Resource Trace File to STDOUT. | ||||
Example: | > mschedctl -n > /tmp/node.trace |
||||
-p — PAUSE | |||||
Format: | --- | ||||
Default: | --- | ||||
Description: | Disable scheduling but allow the scheduler to update its cluster and workload state information. | ||||
Example: | > mschedctl -p |
||||
-R — RECYCLE | |||||
Format: | --- | ||||
Default: | --- | ||||
Description: | Recycle scheduler immediately (shut it down and restart it using the original execution environment and command line arguments). | ||||
Example: | > mschedctl -R
|
||||
-r — RESUME | |||||
Format: | <INTEGER> | ||||
Default: | 0 | ||||
Description: | Resume scheduling at the specified time (or immediately if none is specified). | ||||
Example: | > mschedctl -r |
||||
-s — STOP | |||||
Format: | <INTEGER> | ||||
Default: | 0 | ||||
Description: | Suspend/stop scheduling at specified iteration (or at the end of the current iteration if none is specified). If the letter 'I' follows <ITERATION>, Moab till not process client requests until this iteration is reached. | ||||
Example: | > mschedctl -s 100I |
||||
-S — STEP | |||||
Format: | <INTEGER> | ||||
Default: | 0 | ||||
Description: | Step the specified number of iterations (or to the next iteration if none is specified) and suspend scheduling If the letter 'I' follows <ITERATION>, Moab will not process client requests until this iteration is reached. | ||||
Example: | > mschedctl -S |
Example 1
Shutting down the Scheduler:> mschedctl -k scheduler will be shutdown immediately
Example 2
Creating a virtual private cluster:> mschedctl -c vpc -a resources=14332 -a variables=os=rhel3 vpc.98