LSF Version 7.3 - Administering Platform LSF

Administering Platform LSF 639
Reporting
◆ Windows: LSF_CONFDIR\ego\cluster_name\eservice\esc\conf\
services
Data purger The relational database needs to be kept to a reasonable size to maintain optimal
efficiency. The data purger manages the database size by purging old data at regular
intervals. By default, the data purger purges records older than 14 days at 12:30am
every day.
To reschedule the purging of old data, you can change the purger schedule, as
described in Change the data purger schedule on page 644. To reduce or increase
the number or records in the database, you can change the duration of time that
records are stored in the database, as described in Change the default record expiry
time on page 646. If there are specific tables that are containing too much or too
little data, you can also change the duration of time that records are stored in each
individual table within the database, as described in Change the record expiry time
per table on page 646.
If you edit any
purger configuration files, you need to restart the purger service.
If your cluster has PERF controlled by EGO, you can edit the
purger_service.xml
service configuration file, but you must restart the
purger service and EGO on the
master host after editing the file. The
purger_service.xml file is located in the
EGO service directory:
◆ UNIX: LSF_CONFDIR/ego/cluster_name/eservice/esc/conf/services
◆ Windows: LSF_CONFDIR\ego\cluster_name\eservice\esc\conf\
services
Derby database The Derby database uses the derbydb service. You need to restart this service
manually whenever you change the Derby database settings. The Derby database is
only appropriate for demo clusters. To use the reporting feature to produce regular
reports for a production cluster, you must move to a production database using a
supported commercial database and disable automatic startup of the
derbydb
service, as described in Move to a Production Database on page 505.
Event data files The events logger stores event data in event data files. The EGO allocation event
data file (for EGO-enabled clusters only) is named
ego.stream by default and has
a default maximum size of 10MB. The LSF event data file is named
lsb.stream by
default and has a default maximum size of 100MB. When a data file exceeds this
size, the events logger archives the file and creates a new data file.
The events logger only maintains one archive file and overwrites the old archive
with the new archive. The default archive file name is
ego.stream.0 for EGO and
lsb.stream.0 for LSF. The two LSF files are located in
LSF_TOP/work/cluster_name/logdir/stream by default, and the two EGO files
are located in
LSF_TOP/work/cluster_name/ego/data by default. The event data
loaders read both the data files and the archive files.
If your system logs a large number of events, you should increase the maximum file
size to see more archived event data. If your disk space is insufficient for storing the
four files, you should decrease the maximum file size, or change the file path to a
location with sufficient storage space. Change the disk usage of your LSF event data
files as described in Change the disk usage of LSF event data files on page 643 or the