com.bigdata.service

Interface AbstractTransactionService.Options

All Known Subinterfaces:

DistributedTransactionService.Options

Enclosing class:

AbstractTransactionService

public static interface AbstractTransactionService.Options

Options understood by this service.

Version:

$Id$

Author:

Bryan Thompson

Field Summary

Fields

Modifier and Type	Field and Description
static String	DEFAULT_MIN_RELEASE_AGE Default minimum release age is ONE(1L) milliseconds (only the last commit point will be retained after a full compacting merge).
static String	MIN_RELEASE_AGE How long you want to hold onto the database history (in milliseconds) or Long.MAX_VALUE for an (effectively) immortal database.
static String	MIN_RELEASE_AGE_1D Minimum release age is one day.
static String	MIN_RELEASE_AGE_1H Minimum release age is one hour.
static String	MIN_RELEASE_AGE_1M Minimum release age is one minutes.
static String	MIN_RELEASE_AGE_1W Minimum release age is one week.
static String	MIN_RELEASE_AGE_5M Minimum release age is five minutes.
static String	MIN_RELEASE_AGE_NEVER Immortal database (the release time is set to Long.MAX_VALUE).
static String	MIN_RELEASE_AGE_NO_HISTORY Minimum release age is zero (0).

Field Detail

MIN_RELEASE_AGE

static final String MIN_RELEASE_AGE

How long you want to hold onto the database history (in milliseconds) or Long.MAX_VALUE for an (effectively) immortal database. The ITransactionService tracks the timestamp corresponding to the earliest running transaction (if any). When such a transaction exists, the actual release time is:

 releaseTime = min(lastCommitTime - 1, min(earliestRunningTx, now - minimumReleaseAge))
 

This ensures that history in use by running transactions is not released even when the minimumReleaseAge is ZERO (0).

When no transactions exist the actual release time is:

 releaseTime = min(commitTime - 1, now - minimumReleaseAge)
 

This ensures that the the release time advances when no transactions are in use, but that the minimum release age is still respected.

See Also:

DEFAULT_MIN_RELEASE_AGE, MIN_RELEASE_AGE_1H, MIN_RELEASE_AGE_1D, MIN_RELEASE_AGE_1W, MIN_RELEASE_AGE_NEVER, AbstractTransactionService#updateReleaseTime(long), AbstractTransactionService.notifyCommit(long)

MIN_RELEASE_AGE_NO_HISTORY

static final String MIN_RELEASE_AGE_NO_HISTORY

Minimum release age is zero (0). A value of ZERO (0) implies that any history not required for the read-committed view is released each time the ResourceManager overflows.

See Also:

Constant Field Values

MIN_RELEASE_AGE_1M

static final String MIN_RELEASE_AGE_1M

Minimum release age is one minutes.

See Also:

Constant Field Values

MIN_RELEASE_AGE_5M

static final String MIN_RELEASE_AGE_5M

Minimum release age is five minutes.

See Also:

Constant Field Values

MIN_RELEASE_AGE_1H

static final String MIN_RELEASE_AGE_1H

Minimum release age is one hour.

See Also:

Constant Field Values

MIN_RELEASE_AGE_1D

static final String MIN_RELEASE_AGE_1D

Minimum release age is one day.

See Also:

Constant Field Values

MIN_RELEASE_AGE_1W

static final String MIN_RELEASE_AGE_1W

Minimum release age is one week.

See Also:

Constant Field Values

MIN_RELEASE_AGE_NEVER

static final String MIN_RELEASE_AGE_NEVER

Immortal database (the release time is set to Long.MAX_VALUE).

See Also:

Constant Field Values

DEFAULT_MIN_RELEASE_AGE

static final String DEFAULT_MIN_RELEASE_AGE

Default minimum release age is ONE(1L) milliseconds (only the last commit point will be retained after a full compacting merge). This causes the RWStore to use its recycler mode by default rather than its session protection mode.

See Also:

Change DEFAULT_MIN_RELEASE_AGE to 1ms, Constant Field Values