com.sleepycat.je.cleaner

Class FileProcessor

java.lang.Object

com.sleepycat.je.utilint.DaemonThread

com.sleepycat.je.cleaner.FileProcessor

All Implemented Interfaces:

DaemonRunner, Runnable

public class FileProcessor
extends DaemonThread

Reads all entries in a log file and either determines them to be obsolete or active. Active LNs are migrated immediately (by logging them). Active INs are marked for migration by setting the dirty flag. May be invoked explicitly by calling doClean, or woken up if used as a daemon thread.

Field Summary

Fields inherited from class com.sleepycat.je.utilint.DaemonThread

envImpl, logger, name, nWakeupRequests, stifleExceptionChatter

Method Summary

Modifier and Type	Method and Description
ExpirationTracker	countExpiration(long fileNum) Calculates expired bytes without performing any migration or other side effects.
protected long	nDeadlockRetries() Return the number of retries when a deadlock exception occurs.
protected void	onWakeup() The thread is woken, either by an explicit notify (call to Cleaner.wakeupActivate(), or when the timed wakeup interval elapses.

Methods inherited from class com.sleepycat.je.utilint.DaemonThread

checkErrorListener, createLogger, getNWakeupRequests, getThread, isPaused, isRunning, isShutdownRequested, requestShutdown, run, runOrPause, setWaitTime, shutdown, toString, wakeup

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait

Method Detail

nDeadlockRetries

protected long nDeadlockRetries()

Return the number of retries when a deadlock exception occurs.

Overrides:

nDeadlockRetries in class DaemonThread

onWakeup

protected void onWakeup()

The thread is woken, either by an explicit notify (call to Cleaner.wakeupActivate(), or when the timed wakeup interval elapses. In the former case (a call to wakeupActivate), the 'activate' field will be true and the doClean method is called here. This happens when the number of bytes written exceeds the cleanerBytesInterval, a config change is made that could impact cleaning, etc. In the latter case (the wakeup interval elapsed), 'activate' will be false. In this case, when there has been no writing since the last wakeup, we perform cleaning and checkpointing, if needed to reclaim space. This handles the situation where writing stops, but cleaning or checkpointing or reserved file deletion may be needed. See EnvironmentConfig.CLEANER_WAKEUP_INTERVAL. In all cases, when a disk limit is in violation we always call the doClean method to ensure that Cleaner.manageDiskUsage() is called in this situation. This is important to free disk space whenever possible.

Specified by:

onWakeup in class DaemonThread

countExpiration

public ExpirationTracker countExpiration(long fileNum)

Calculates expired bytes without performing any migration or other side effects. The expired sizes will not overlap with obsolete data, because expired sizes are accumulated only for non-obsolete entries.

Parameters:

fileNum - file to read.

Returns:

the expiration tracker.