async-store-manager

`async-store-manager`

Used in: external-scheme, paged-external-scheme.

Description

The async-store-manager element adds asynchronous write capabilities to other store manager implementations.

Supported store managers include:

custom-store-manager - allows definition of custom implementations of store managers
bdb-store-manager - uses Berkeley Database JE to implement an on-disk cache
lh-file-manager - uses a Coherence LH on-disk database cache
nio-file-manager - uses NIO to implement memory-mapped file based cache
nio-memory-manager - uses NIO to implement an off JVM heap, in-memory cache

Implementation

This store manager is implemented by the com.tangosol.io.AsyncBinaryStoreManager class.

Elements

The following table describes the elements you can define within the async-store-manager element.

Element	Required/Optional	Description
`<class-name>`	Optional	Specifies a custom implementation of the `async-store-manager`. Any custom implementation must extend the `com.tangosol.io.AsyncBinaryStoreManager` class and declare the exact same set of public constructors.
`<init-params>`	Optional	Specifies initialization parameters, for use in custom `async-store-manager` implementations which implement the `com.tangosol.run.xml.XmlConfigurable` interface.
`<custom-store-manager>`	Optional	Configures the external cache to use a custom storage manager implementation.
`<bdb-store-manager>`	Optional	Configures the external cache to use Berkeley Database JE on-disk databases for cache storage.
`<lh-file-manager>`	Optional	Configures the external cache to use a Coherence LH on-disk database for cache storage.
`<nio-file-manager>`	Optional	Configures the external cache to use a memory-mapped file for cache storage.
`<nio-memory-manager>`	Optional	Configures the external cache to use an off JVM heap, memory region for cache storage.
`<async-limit>`	Optional	Specifies the maximum number of bytes that will be queued to be written asynchronously. Setting the value to zero does not disable the asynchronous writes; instead, it indicates that the implementation default for the maximum number of bytes should be used. The value of this element must be in the following format: [\d]+[[.][\d]+]?[K\|k\|M\|m]?[B\|b]? where the first non-digit (from left to right) indicates the factor with which the preceeding decimal value should be multiplied: `K (kilo, 2¹⁰)` `M (mega, 2²⁰)` If the value does not contain a factor, a factor of one is assumed. Valid values are any positive memory sizes and {{zero. Default value is `4MB`.