Platform LSF Administration Guide Version 6.2

Duplicate Logging of Event Logs
Administering Platform LSF
596
events to LSB_LOCALDIR and M2 logging to LSB_SHAREDIR. When connectivity is
restored, the changes made by M2 to
LSB_SHAREDIR will be lost when M1 updates
LSB_SHAREDIR from its copy in LSB_LOCALDIR.
The archived event files are only available on
LSB_LOCALDIR, so in the case of network
partitioning, commands such as
bhist cannot access these files. As a precaution, you
should periodically copy the archived files from
LSB_LOCALDIR to LSB_SHAREDIR.
Setting an event
update interval
If NFS traffic is too high and you want to reduce network traffic, use
EVENT_UPDATE_INTERVAL in
lsb.params to specify how often to back up the
data and synchronize the LSB_SHAREDIR and LSB_LOCALDIR directories.
The directories are always synchronized when data is logged to the files, or when
mbatchd is started on the first LSF master host.
Automatic archiving and duplicate logging
Event logs
Archived event logs, lsb.events.n, are not replicated to LSB_SHAREDIR. If LSF
starts a new event log while the file server containing
LSB_SHAREDIR is down, you
might notice a gap in the historical data in
LSB_SHAREDIR.
Configuring duplicate logging
To enable duplicate logging, set LSB_LOCALDIR in lsf.conf to a directory on the
first master host (the first host configured in
lsf.cluster.cluster_name) that will be
used to store the primary copies of
lsb.events. This directory should only exist on
the first master host.
1 Edit lsf.conf and set LSB_LOCALDIR to a local directory that exists only on
the first master host.
2 Use the commands lsadmin reconfig and badmin mbdrestart to make the
changes take effect.