LSF Version 7.3 - Administering Platform LSF

Controlling mbatchd
52 Administering Platform LSF
Controlling mbatchd
You use the badmin command to control mbatchd.
Reconfigure mbatchd
If you add a host to a host group, a host to a queue, or change resource configuration
in the Hosts section of
lsf.cluster.cluster_name, the change is not recognized by
jobs that were submitted before you reconfigured. If you want the new host to be
recognized, you must restart
mbatchd.
1 Run badmin reconfig.
When you reconfigure the cluster,
mbatchd is not restarted. Only configuration
files are reloaded.
Restart mbatchd
1 Run badmin mbdrestart.
LSF checks configuration files for errors and prints the results to
stderr. If no
errors are found, the following occurs:
◆ Configuration files are reloaded
◆ mbatchd is restarted
◆ Events in lsb.events are reread and replayed to recover the running state
of the last mbatchd
TIP: Whenever mbatchd is restarted, it is unavailable to service requests. In large clusters where
there are many events in lsb.events, restarting mbatchd can take some time. To avoid
replaying events in lsb.events, use the command badmin reconfig.
Log a comment when restarting mbatchd
1 Use the -C option of badmin mbdrestart to log an administrator comment in
lsb.events.
For example:
badmin mbdrestart -C "Configuration change"
The comment text Configuration change is recorded in lsb.events.
2 Run
badmin hist or badmin mbdhist to display administrator comments for
mbatchd restart.