此内容没有您所选择的语言版本。
Chapter 18. Cache Writing Modes
Red Hat JBoss Data Grid presents configuration options with a single or multiple cache stores. This allows it to store data in a persistent location, for example a shared JDBC database or a local file system. JBoss Data Grid supports two caching modes:
- Write-Through (Synchronous)
- Write-Behind (Asynchronous)
18.1. Write-Through Caching 复制链接链接已复制到粘贴板!
复制链接链接已复制到粘贴板!
The Write-Through (or Synchronous) mode in Red Hat JBoss Data Grid ensures that when clients update a cache entry (usually via a
Cache.put()
invocation), the call does not return until JBoss Data Grid has located and updated the underlying cache store. This feature allows updates to the cache store to be concluded within the client thread boundaries.
18.1.1. Write-Through Caching Benefits 复制链接链接已复制到粘贴板!
复制链接链接已复制到粘贴板!
The primary advantage of the Write-Through mode is that the cache and cache store are updated simultaneously, which ensures that the cache store remains consistent with the cache contents. This is at the cost of reduced performance for cache operations caused by the cache store accesses and updates during cache operations.
No specific configuration operations are required to configure a Write-Through or synchronous cache store. All cache stores are Write-Through or synchronous unless explicitly marked as Write-Behind or asynchronous. The following procedure demonstrates a sample configuration file of a Write-Through unshared local file cache store.
Procedure 18.1. Configure a Write-Through Local File Cache Store
Identify the
namedCache
Thename
parameter specifies the name of thenamedCache
to use.Copy to Clipboard Copied! Toggle word wrap Toggle overflow Configure the Cache Loader
Theshared
parameter is used when multiple cache instances share a cache store. This parameter can be set to prevent multiple cache instances writing the same modification multiple times. Valid values for this parameter aretrue
andfalse
.Copy to Clipboard Copied! Toggle word wrap Toggle overflow Specify the Loader Class
Theclass
attribute defines the class of the cache loader implementation.Copy to Clipboard Copied! Toggle word wrap Toggle overflow Configure the
fetchPersistentState
ParameterThefetchPersistentState
parameter determines whether the persistent state is fetched when joining a cluster. Set this totrue
if using a replication and invalidation in a clustered environment. Additionally, if multiple cache stores are chained, only one cache store can have this property enabled. If a shared cache store is used, the cache does not allow a persistent state transfer despite this property being set totrue
. ThefetchPersistentState
parameter isfalse
by default.Copy to Clipboard Copied! Toggle word wrap Toggle overflow Set the
ignoreModifications
ParameterTheignoreModifications
parameter determines whether operations that modify the cache (e.g. put, remove, clear, store, etc.) do not affect the cache store. As a result, the cache store can become out of sync with the cache.Copy to Clipboard Copied! Toggle word wrap Toggle overflow Configure Purge On Startup
ThepurgeOnStartup
parameter specifies whether the cache is purged when initially started.Copy to Clipboard Copied! Toggle word wrap Toggle overflow The
property
ElementTheproperty
element contains information about properties related to the cache store.- The
name
parameter specifies the name of the property.
Copy to Clipboard Copied! Toggle word wrap Toggle overflow