Administering Platform LSF - SAS

Controlling mbatchd
Controlling mbatchd
Restarting mbatchd
When you reconfigure the cluster with the command badmin reconfig,
mbatchd is not restarted. Only configuration files are reloaded.
If you add a host to a host group, or a host to a queue, the new host is not
recognized by jobs that were submitted before you reconfigured. If you want
the new host to be recognized, you must restart mbatchd.
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.
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.
Logging a comment when restarting mbatchd
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.
Use badmin hist or badmin mbdhist to display administrator comments for
mbatchd restart.
Shutting down mbatchd
1 Run badmin hshutdown to shut down sbatchd on the master host. For
example:
% badmin hshutdown hostD
Shut down slave batch daemon on .... done
2 Run badmin mbdrestart:
% badmin mbdrestart
Checking configuration files ...
No errors found.
This causes mbatchd and mbschd to exit. mbatchd cannot be restarted,
because sbatchd is shut down. All LSF services are temporarily
unavailable, but existing jobs are not affected. When mbatchd is later
started by sbatchd, its previous status is restored from the event log file
and job scheduling continues.
64
Administering Platform LSF