schema.jboss-as-infinispan_1_4.xsd Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of wildfly-clustering-infinispan-extension Show documentation
Show all versions of wildfly-clustering-infinispan-extension Show documentation
Installs an extension that provides the infinispan subsystem.
Enumerates the cache containers available to the registry.
Defines an embedded cache container.
Overrides the transport characteristics for this cache container.
Defines a LOCAL mode cache.
Defines a REPL_* mode cache.
Defines an INVALIDATION_* mode cache.
Defines a DIST_* mode cache.
Uniquely identifies this cache container.
A set of aliases by which this cache container may also be referenced.
The jndi name to which to bind this cache container.
If undefined, the cache will be bound to: java:jboss/infinispan/container/container-name
Indicates the default cache for this cache container.
Should this cache container be started on server startup, or lazily when requested by a service or deployment.
Defines the executor used for asynchronous cache listener notifications.
Defines the scheduled executor used for evictions.
Defines the scheduled executor used by the asynchronous replication queue.
Defines the module whose class loader should be used when building this cache container.
Defines the jgroups stack used by the transport.
Defines the name for the underlying group communication cluster.
Defines the executor used for asynchronous transport communication.
Infinispan uses a distributed lock to maintain a coherent transaction log during state transfer or rehashing, which means that only one cache can be doing state transfer or rehashing at the same time.
This constraint is in place because more than one cache could be involved in a transaction.
This timeout controls the time to wait to acquire acquire a lock on the distributed lock.
The locking configuration of the cache.
The cache transaction configuration.
The cache eviction configuration.
The cache expiration configuration.
Defines a custom cache store.
Defines a file-based cache store.
Defines a database cache store accessed via JDBC using string-based keys.
Defines a database cache store accessed via JDBC using binary-based keys.
Defines a database cache store accessed via JDBC using mixed string and binary-based keys.
Defines a remote cache store accessed via HotRod.
Nested properties will be treated as HotRod client properties.
defined indexing options for cache
Property to pass on to the indexing system.
The indexing mode of the cache. Defaults to NONE.
Uniquely identifies this cache within its cache container.
Should this cache be started on server startup, or lazily when requested by a service or deployment.
Use batching to group cache operations together. Defaults to false.
The jndi name to which to bind this cache.
If undefined, the cache will be bound to: java:jboss/infinispan/cache/container-name/cache-name
Defines the module whose class loader should be used when building this cache, if different from the enclosing cache container.
Sets the cache locking isolation level.
If true, a pool of shared locks is maintained for all entries that need to be locked. Otherwise, a lock is created per entry in the cache. Lock striping helps control memory footprint but may reduce concurrency in the system.
Maximum time to attempt a particular lock acquisition.
Concurrency level for lock containers. Adjust this value according to the number of concurrent threads interacting with Infinispan.
Sets the cache transaction mode to one of NONE, NON_XA, NON_DURABLE_XA, FULL_XA.
If there are any ongoing transactions when a cache is stopped, Infinispan waits for ongoing remote and local transactions to finish. The amount of time to wait for is defined by the cache stop timeout.
The locking mode for this cache, one of OPTIMISTIC or PESSIMISTIC.
Sets the cache eviction strategy. Available options are 'UNORDERED', 'FIFO', 'LRU', 'LIRS' and 'NONE' (to disable eviction).
Maximum number of entries in a cache instance. If selected value is not a power of two the actual value will default to the least power of two larger than selected value. -1 means no limit.
Maximum idle time a cache entry will be maintained in the cache, in milliseconds. If the idle time is exceeded, the entry will be expired cluster-wide. -1 means the entries never expire.
Maximum lifespan of a cache entry, after which the entry is expired cluster-wide, in milliseconds. -1 means the entries never expire.
Interval (in milliseconds) between subsequent runs to purge expired entries from memory and any cache stores. If you wish to disable the periodic eviction process altogether, set wakeupInterval to -1.
Enables the use of asynchronous marshalling
Sets the clustered cache mode, ASYNC for asynchronous operation, or SYNC for synchronous operation.
In ASYNC mode, this attribute can be used to trigger flushing of the queue when it reaches a specific threshold.
In ASYNC mode, this attribute controls how often the asynchronous thread used to flush the replication queue runs. This should be a positive integer which represents thread wakeup time in milliseconds.
In SYNC mode, the timeout (in ms) used to wait for an acknowledgment when making a remote call, after which the call is aborted and an exception is thrown.
The state transfer configuration for distribution and replicated caches.
Number of cluster-wide replicas for each cache entry.
Number of hash space segments (per cluster).
Maximum lifespan in milliseconds of an entry placed in the L1 cache.
Configures a cache store as write-behind instead of write-through.
A cache store property with name and value.
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.
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.
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. 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.
If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
If true, purges this cache store when it starts up.
If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through.
until it can accept new entries
Timeout in milliseconds to stop the cache store.
Size of the thread pool whose threads are responsible for applying the modifications to the cache store.
The class name of the cache store implementation.
The base directory in which to store the cache state.
The path within "relative-to" in which to store the cache state.
If undefined, the path defaults to the cache container name.
The name of the remote cache. If undefined, the default cache will be used.
Enable/disable SO_TIMEOUT on socket connections to remote Hot Rod servers with the specified timeout, in milliseconds.
A timeout of zero is interpreted as an infinite timeout.
Enable/disable TCP_NODELAY on socket connections to remote Hot Rod servers.
An outbound socket binding for a remote server.
Defines the table used to store cache entries.
Defines the jndi name of the datasource.
Defines the table used to store cache buckets.
Defines the jndi name of the datasource.
Defines the table used to store cache buckets.
Defines the table used to store cache entries.
Defines the jndi name of the datasource.
Defines the prefix prepended to the cache name used when composing the name of the cache entry table.
Defines the prefix prepended to the cache name used when composing the name of the cache bucket table.
Defines the column in which to store the cache key or bucket id.
Defines the column in which to store the cache entry or bucket.
Defines the column in which to store the timestamp of the cache entry or bucket.
The fetch size used when querying from this table. Used to avoid heap memory exhaustion when query is large.
The statement batch size used when modifying this table.
The name of the column used to store the cache key or bucket id.
The type of the column used to store the cache key or bucket id.
The name of the column used to store the cache entry or bucket.
The type of the column used to store the cache entry or bucket.
The name of the column used to store the cache entry or bucket timestamp.
The type of the column used to store the cache entry or bucket timestamp.
If enabled, this will cause the cache to ask neighboring caches for state when it starts up, so the cache starts 'warm', although it will impact startup time.
The maximum amount of time (ms) to wait for state from neighboring caches, before throwing an exception and aborting startup.
The number of cache entries to batch in each transfer.
Defines the name of a property.
No locking isolation will be performed. This is only valid in local mode. In clustered mode, READ_COMMITTED will be used instead.
Unsupported. Actually configures READ_COMMITTED.
Read committed is an isolation level that guarantees that any data read is committed at the moment it is read. However, depending on the outcome of other transactions, successive reads may return different results.
Repeatable read is an isolation level that guarantees that any data read is committed at the moment it is read and that, within a transaction, successive reads will always return the same data.
Unsupported. Actually configures REPEATABLE_READ.
Cache will not enlist within transactions.
Cache will enlist within transactions as a javax.transaction.Synchronization
Cache will enlist within transactions as a javax.transaction.xa.XAResource, without recovery.
Cache will enlist within transactions as a javax.transaction.xa.XAResource, with recovery.
Do not index data. This is the default.
Only index changes made locally, ignoring remote changes. This is useful if indexes are shared across a cluster to prevent redundant indexing of updates.
Index all data.
Never evict entries. This is the default.
Actually activates LRU.
Deprecated. Actually activates LRU.
Least-Recently Used policy.
Low Inter-reference Recency Set. An improved version of LRU which uses cache-locality access information to better decide which data to evict.
Enables asynchronous mode.
Enables synchronous mode.
Enables Optimistic locking.
Enables Pessimistic locking.
Start the cache container on server startup.
Start the cache container lazily when requested by a service or deployment.
A list of aliases.