Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
add an example of a chained infinispan configuration
- Loading branch information
Showing
1 changed file
with
110 additions
and
0 deletions.
There are no files selected for viewing
110 changes: 110 additions & 0 deletions
110
fcrepo-webapp/src/main/resources/config/infinispan_configuration_chained.xml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,110 @@ | ||
| <infinispan xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | ||
| xsi:schemaLocation="urn:infinispan:config:5.2 http://www.infinispan.org/schemas/infinispan-config-5.2.xsd" | ||
| xmlns="urn:infinispan:config:5.2"> | ||
|
|
||
| <global> | ||
| <!-- Defines the global settings shared by all caches --> | ||
| <transport> | ||
| <properties> | ||
| <property name="configurationFile" value="${fcrepo.ispn.jgroups.configuration:config/jgroups-infinispan.xml}"/> | ||
| </properties> | ||
| </transport> | ||
| </global> | ||
|
|
||
| <default> | ||
| <!-- | ||
| Defines the default behavior for all caches, including those created dynamically (e.g., when a | ||
| repository uses a cache that doesn't exist in this configuration). | ||
| --> | ||
| <clustering mode="distribution"> | ||
| <sync/> | ||
| <l1 enabled="false" lifespan="0" onRehash="false"/> | ||
| <hash numOwners="1"/> | ||
| <stateTransfer fetchInMemoryState="true"/> | ||
| </clustering> | ||
| </default> | ||
|
|
||
| <namedCache name="FedoraRepository"> | ||
| <!-- | ||
| Our Infinispan cache needs to be transactional. However, we'll also configure it to | ||
| use pessimistic locking, which is required whenever applications will be concurrently | ||
| updating nodes within the same process. If you're not sure, use pessimistic locking. | ||
| --> | ||
| <clustering mode="distribution"> | ||
| <sync/> | ||
| <l1 enabled="false" lifespan="0" onRehash="false"/> | ||
| <hash numOwners="1"/> | ||
| <stateTransfer fetchInMemoryState="true"/> | ||
| </clustering> | ||
|
|
||
| <eviction maxEntries="100" strategy="LRU" threadPolicy="DEFAULT"/> | ||
|
|
||
| <transaction | ||
| transactionManagerLookupClass="org.infinispan.transaction.lookup.GenericTransactionManagerLookup" | ||
| transactionMode="TRANSACTIONAL" lockingMode="PESSIMISTIC"/> | ||
| <!-- | ||
| Define the cache loaders (i.e., cache stores). Passivation is false because we want *all* | ||
| data to be persisted, not just what doesn't fit into memory. Shared is false because there | ||
| are no other caches sharing this file store. We set preload to false for lazy loading; | ||
| may be improved by preloading and configuring eviction. | ||
| We can have multiple cache loaders, which get chained. But we'll define just one. | ||
| --> | ||
|
|
||
| <loaders passivation="false" shared="false" preload="false"> | ||
|
|
||
| <!-- | ||
| The 'fetchPersistentState' attribute applies when this cache joins the cluster; the value doesn't | ||
| really matter to us in this case. See the documentation for more options. | ||
| --> | ||
| <loader class="org.infinispan.loaders.file.FileCacheStore" fetchPersistentState="true" | ||
| purgeOnStartup="false"> | ||
| <!-- See the documentation for more configuration examples and flags. --> | ||
| <properties> | ||
| <!-- We have to set the location where we want to store the data. --> | ||
| <property name="location" value="${fcrepo.ispn.CacheDirPath:target/FedoraRepository/storage}"/> | ||
|
|
||
| <property name="fsyncMode" value="perWrite"/> | ||
| </properties> | ||
| <!-- This repository isn't clustered, so we could set up the SingletonStore. | ||
| singletonStore enabled="true" pushStateWhenCoordinator="true" pushStateTimeout="20000"/> | ||
| --> | ||
| <!-- | ||
| We could use "write-behind", which actually writes to the file system asynchronously, | ||
| which can improve performance as seen by the JCR client. | ||
| Plus changes are coalesced, meaning that if multiple changes are enqueued for the | ||
| same node, only the last one is written. (This is good much of the time, but not | ||
| always.) | ||
| <async enabled="true" flushLockTimeout="15000" threadPoolSize="5"/> | ||
| --> | ||
| </loader> | ||
|
|
||
| <!-- | ||
| The 'fetchPersistentState' attribute applies when this cache joins the cluster; the value doesn't | ||
| really matter to us in this case. See the documentation for more options. | ||
| --> | ||
| <loader class="org.infinispan.loaders.file.FileCacheStore" fetchPersistentState="false" | ||
| purgeOnStartup="false"> | ||
| <!-- See the documentation for more configuration examples and flags. --> | ||
| <properties> | ||
| <!-- We have to set the location where we want to store the data. --> | ||
| <property name="location" value="${fcrepo.ispn.alternative.CacheDirPath:target/FedoraRepository/storage-alt}"/> | ||
|
|
||
| <property name="fsyncMode" value="perWrite"/> | ||
| </properties> | ||
| <!-- This repository isn't clustered, so we could set up the SingletonStore. | ||
| singletonStore enabled="true" pushStateWhenCoordinator="true" pushStateTimeout="20000"/> | ||
| --> | ||
| <!-- | ||
| We could use "write-behind", which actually writes to the file system asynchronously, | ||
| which can improve performance as seen by the JCR client. | ||
| Plus changes are coalesced, meaning that if multiple changes are enqueued for the | ||
| same node, only the last one is written. (This is good much of the time, but not | ||
| always.) | ||
| --> | ||
| <async enabled="true" flushLockTimeout="15000" threadPoolSize="5"/> | ||
|
|
||
| </loader> | ||
| </loaders> | ||
| </namedCache> | ||
| </infinispan> |