org.infinispan.config
Interface Configuration.LoadersConfig

All Known Implementing Classes:
CacheLoaderManagerConfig
Enclosing class:
Configuration

public static interface Configuration.LoadersConfig

Holds the configuration for cache loaders and stores.

Since:
5.0
Author:
Vladimir Blagojevic

Method Summary
 Configuration.LoadersConfig addCacheLoaderConfig(CacheLoaderConfig clc)
           
 Configuration.LoadersConfig passivation(Boolean passivation)
          If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'.
 Configuration.LoadersConfig preload(Boolean preload)
          If true, when the cache starts, data stored in the cache store will be pre-loaded into memory.
 Configuration.LoadersConfig setCacheLoaderConfigs(List<CacheLoaderConfig> configs)
           
 Configuration.LoadersConfig shared(Boolean shared)
          This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times.
 

Method Detail

preload

Configuration.LoadersConfig preload(Boolean preload)
If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.

Parameters:
preload -

passivation

Configuration.LoadersConfig passivation(Boolean passivation)
If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. This gives you the ability to 'overflow' to disk, similar to swapping in an operating system.

If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.

Parameters:
passivation -

shared

Configuration.LoadersConfig shared(Boolean shared)
This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store.

If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store. Note that this could be useful if each individual node has its own cache store - perhaps local on-disk.

Parameters:
shared -

addCacheLoaderConfig

Configuration.LoadersConfig addCacheLoaderConfig(CacheLoaderConfig clc)

setCacheLoaderConfigs

Configuration.LoadersConfig setCacheLoaderConfigs(List<CacheLoaderConfig> configs)


Copyright © 2011 JBoss, a division of Red Hat. All Rights Reserved.