Librarian Configuration Options
The following options affect the operations of the archive librarian. Automatically enable historical archive record indexing to a database by setting use feature:librarian.
- USING_LIBRARIAN¶
A boolean value representing whether or not the archive librarian is in use for tools to utilize for faster archive queries. Defaults to
False.- LIBRARIAN¶
The path to the condor_librarian executable. Defaults to
$(SBIN)/condor_librarian.- LIBRARIAN_LOG¶
The path to the archive librarian’s debug file. Defaults to
$(LOG)/LibrarianLog.- MAX_LIBRARIAN_LOG¶
The maximum size of the archive librarian’s debug file before being rotated. Defaults to MAX_DEFAULT_LOG.
- LIBRARIAN_DEBUG¶
The archive librarian’s debugging level. Default is nothing.
- LIBRARIAN_DATABASE¶
The path to the archive librarian’s SQLite3 database file. Defaults to
$(SPOOL)/library.db.- LIBRARIAN_MAX_DATABASE_SIZE¶
A 64-bit integer representing the maximum size of the archive librarian’s database file. This defaults to
2GB.- LIBRARIAN_HIGH_WATER_MARK¶
A floating point number between the range of 0 and 1 that represents a percent value threshold of garbage collection trigger size in the database i.e. a max size of
2GBwith a high water mark of0.75would trigger garbage collection once the database becomes1.5GBor larger. Default is0.97.- LIBRARIAN_LOW_WATER_MARK¶
A floating point number between the range of 0 and 1 that represents a percent value threshold to attempt reducing the archive librarian’s database size during garbage collection i.e. a max size of
2GBwith a low water mark of0.5will try to reduce the database size to or below1GBduring garbage collection. Default is0.8.The database file uses SQLite’s incremental auto-vacuum mode so that garbage collection actually shrinks the file on disk, rather than only freeing internal space for reuse. The first time the archive librarian starts against an existing database that predates this mode, it performs a one-time full
VACUUMto convert it; this copies the entire database and can take a while for a large file, but only happens once.- LIBRARIAN_GC_BACKOFF_SECONDS¶
An integer value representing how long, in seconds, to wait before retrying garbage collection after a pass that did not reduce the database’s file size. Defaults to
1800(30 minutes).- LIBRARIAN_MAX_JOBS_CACHED¶
An integer value representing the maximum number of job id information to database reference id’s to cache in memory. Defaults to
10,000.- LIBRARIAN_MAX_UPDATES_PER_CYCLE¶
A 64-bit integer representing the maximum number of new archive record index insertions into the archive librarian’s database per update interval. Defaults to
100,000.- LIBRARIAN_STATUS_RETENTION_SECONDS¶
An integer value representing the lifetime in seconds of per update interval status entries within the archive librarian’s database. Defaults to
300or 5 minutes.- LIBRARIAN_UPDATE_INTERVAL¶
An integer value representing the time interval in seconds between the archive librarians main actions of scanning archive files for new records and updating the database with indexes. Defaults to
5.- LIBRARIAN_DATABASE_BUSY_TIMEOUT_MS¶
An integer value representing how long, in milliseconds, the archive librarian will wait on a locked SQLite3 database before giving up. Since the database runs in WAL mode, ordinary reads and writes are not affected by this setting; it only comes into play for the periodic WAL checkpoint and for the
VACUUM/incremental_vacuumoperations used to reclaim disk space, where a lingering reader can transiently hold a lock. Must be0or greater. Defaults to30000(30 seconds).