Skip navigation links

com.tangosol.io.journal
Interface AbstractJournalRM.Dependencies

All Known Subinterfaces:

FlashJournalRM.Dependencies, RamJournalRM.Dependencies

All Known Implementing Classes:

AbstractJournalRM.DefaultDependencies, FlashJournalRM.DefaultDependencies, RamJournalRM.DefaultDependencies

Enclosing class:

AbstractJournalRM

protected static interface AbstractJournalRM.Dependencies

The Dependencies interface provides AbstractJournalRM with its external dependencies.

Method Summary

double	getCollectorLoadFactor() Return the load factor threshold at which files become eligible for garbage collection (compaction).
long	getMaxFileSize() Return the maximum allowable size, in bytes, of each individual file used to hold Journal data.
int	getMaxValueSize() Return the maximum allowable size, in bytes, of a Binary value.

Method Detail

getMaxValueSize

int getMaxValueSize()

Return the maximum allowable size, in bytes, of a Binary value.

Returns:

the maximum allowable size for a value to write

getMaxFileSize

long getMaxFileSize()

Return the maximum allowable size, in bytes, of each individual file used to hold Journal data. This is not the total size limit of the Journal, since the Journal may use a number of files to store its data.

Returns:

the maximum allowable size for an underlying file

getCollectorLoadFactor

double getCollectorLoadFactor()

Return the load factor threshold at which files become eligible for garbage collection (compaction). The load factor threshold is the ratio between the portion of the file used for live data and the total size of the file, and is expressed as a double value in the interval (0.0, 1.0).

When the portion of released data exceeds (1 - threshold), the file becomes eligible for compaction (garbage collection).

Returns:

the compaction factor threshold between 0.0 and 1.0

Skip navigation links