LSF Version 7.3 - Administering Platform LSF

Reconfiguring your cluster
56 Administering Platform LSF
If no errors are found, you are prompted to either restart lim on master host
candidates only, or to confirm that you want to restart
lim on all hosts. If fatal
errors are found, reconfiguration is aborted.
3 Run
badmin reconfig to reconfigure mbatchd:
badmin reconfig
The badmin reconfig command checks for configuration errors.
If fatal errors are found, reconfiguration is aborted.
Reconfigure the cluster by restarting mbatchd
To replay and recover the running state of the cluster, use this method to
reconfigure the cluster.
1 Run badmin mbdrestart to restart mbatchd:
badmin mbdrestart
The badmin mbdrestart command checks for configuration errors.
If no fatal errors are found, you are asked to confirm
mbatchd restart. If fatal
errors are found, the command exits without taking any action.
TIP: If the lsb.events file is large, or many jobs are running, restarting mbatchd can take
some time. In addition, mbatchd is not available to service requests while it is restarted.
View configuration errors
1 Run lsadmin ckconfig -v.
2 Run badmin ckconfig -v.
This reports all errors to your terminal.
How reconfiguring the cluster affects licenses
If the license server goes down, LSF can continue to operate for a period of time
until it attempts to renew licenses.
Reconfiguring causes LSF to renew licenses. If no license server is available, LSF
does not reconfigure the system because the system would lose all its licenses and
stop working.
If you have multiple license servers, reconfiguration proceeds provided LSF can
contact at least one license server. In this case, LSF still loses the licenses on servers
that are down, so LSF may have fewer licenses available after reconfiguration.