public interface JournalMBean
JournalMBean
is an MBean interface providing statistics for a Journal Resource Manager as implemented by either FlashJournalRM
or RamJournalRM
implementations.Modifier and Type | Method and Description |
---|---|
void |
compact(boolean fRegular)
Execute either a regular or exhaustive compaction on the journal based on the provided parameter.
|
int |
getBacklogCount()
Determine the number of serialized values that have not yet been persisted to disk.
|
int |
getBacklogSize()
Determine the total size in bytes of the serialized values that have not yet been persisted to disk.
|
int |
getBinaryStoreCount()
Determine the number of active BinaryStore objects that are using this Journal.
|
int |
getBufferSize()
Determine the size of the buffers used to write a chunk of data at a time to an underlying journal file.
|
double |
getCollectorLoadFactor()
Determine the load factor threshold at which files become eligible for garbage collection (compaction).
|
int |
getCompactionCount()
Determine the number of compactions (garbage collections) performed by this journal.
|
double |
getCurrentCollectorLoadFactor()
Determine the current load factor threshold for the journal.
|
int |
getExhaustiveCompactionCount()
Determine the total number of exhaustive compactions performed by the collector.
|
long |
getExhaustiveCompactionTime()
Return the total amount time spent performing exhaustive compaction.
|
int |
getFileCount()
Determine the number of Journal files used by this Journal.
|
double |
getHighestLoadFactor()
Determine the high-water mark load factor for the entire journal.
|
int |
getHighFileCount()
Determine the high file count for this Journal.
|
int |
getMaxBacklogSize()
Determine the maximum allowable size, in bytes, of the backlog; when the backlog reaches this level, writes are delayed until the backlog drops below its maximum.
|
long |
getMaxFileSize()
Determine the maximum allowable size, in bytes, of each individual file used to hold Journal data.
|
int |
getMaxJournalFilesNumber()
Determine the maximum number of Journal files.
|
long |
getMaxPoolSize()
Determine the maximum size (in bytes) of the buffers that can be held by the pool.
|
long |
getMaxTotalRam()
Determine the total amount, in bytes, of RAM that will be used for the Journal.
|
int |
getMaxValueSize()
Determine the maximum allowable size, in bytes, of a Binary value.
|
int |
getPoolSize()
Determine the size (in bytes) of the buffers that are currently available in the pool.
|
long |
getTotalDataSize()
Determine the amount of data currently stored by this Journal.
|
long |
getTotalFileSize()
Determine the number of bytes in the Journal files for this Journal.
|
boolean |
isNioRam()
Determine if the journal will use direct buffers (NIO RAM) instead of on-heap buffers (byte arrays).
|
void |
resetStatistics()
Reset the journal statistics.
|
long getMaxFileSize()
int getMaxValueSize()
int getMaxJournalFilesNumber()
int getBinaryStoreCount()
int getFileCount()
int getHighFileCount()
This property is specific to a FlashJournalRM
implementation.
long getTotalDataSize()
long getTotalFileSize()
double getCollectorLoadFactor()
When the portion of released data exceeds (1 - threshold), the file becomes eligible for compaction (garbage collection).
double getCurrentCollectorLoadFactor()
double getHighestLoadFactor()
int getBacklogCount()
This property is specific to a FlashJournalRM
implementation.
int getBacklogSize()
This property is specific to a FlashJournalRM
implementation.
int getMaxBacklogSize()
This property is specific to a FlashJournalRM
implementation.
int getPoolSize()
This property is specific to a FlashJournalRM
implementation.
int getBufferSize()
This property is specific to a FlashJournalRM
implementation.
long getMaxPoolSize()
long getMaxTotalRam()
This property is specific to a RamJournalRM
implementation.
boolean isNioRam()
This property is specific to a RamJournalRM
implementation.
int getCompactionCount()
int getExhaustiveCompactionCount()
long getExhaustiveCompactionTime()
void resetStatistics()
void compact(boolean fRegular)
An exhaustive compaction is only executed if sufficient memory has been released or sufficient time has elapsed since the previous exhaustive compaction.
fRegular
- whether the compaction should be regular; false for an exhaustive compaction