## 1. Infinispan Caches

Infinispan caches provide flexible, in-memory data stores that you can configure to suit use cases such as:

• boosting application performance with high-speed local caches.

• optimizing databases by decreasing the volume of write operations.

• providing resiliency and durability for consistent data across clusters.

### 1.1. Cache Interface

`Cache<K,​V>` is the central interface for Infinispan and extends `java.util.concurrent.ConcurrentMap`.

Cache entries are highly concurrent data structures in `key:value` format that support a wide and configurable range of data types, from simple strings to much more complex objects.

### 1.2. Cache Managers

Infinispan provides a `CacheManager` interface that lets you create, modify, and manage local or clustered caches. Cache Managers are the starting point for using Infinispan caches.

There are two `CacheManager` implementations:

`EmbeddedCacheManager`

Entry point for caches when running Infinispan inside the same Java Virtual Machine (JVM) as the client application, which is also known as Library Mode.

`RemoteCacheManager`

Entry point for caches when running Infinispan as a remote server in its own JVM. When it starts running, `RemoteCacheManager` establishes a persistent TCP connection to a Hot Rod endpoint on a Infinispan server.

 Both embedded and remote `CacheManager` implementations share some methods and properties. However, semantic differences do exist between `EmbeddedCacheManager` and `RemoteCacheManager`.

### 1.3. Cache Containers

Cache containers declare one or more local or clustered caches that a Cache Manager controls.

Cache container declaration
``````<cache-container name="clustered" default-cache="default">
...
</cache-container>``````

### 1.4. Cache Modes

 Infinispan Cache Managers can create and control multiple caches that use different modes. For example, you can use the same Cache Manager for local caches, distributes caches, and caches with invalidation mode.
Local Caches

Infinispan runs as a single node and never replicates read or write operations on cache entries.

Clustered Caches

Infinispan instances running on the same network can automatically discover each other and form clusters to handle cache operations.

Invalidation Mode

Rather than replicating cache entries across the cluser, Infinispan evicts stale data from all nodes whenever operations modify entries in the cache. Infinispan performs local read operations only.

Replicated Caches

Infinispan replicates each cache entry on all nodes and performs local read operations only.

Distributed Caches

Infinispan stores cache entries across a subset of nodes and assigns entries to fixed owner nodes. Infinispan requests read operations from owner nodes to ensure it returns the correct value.

Scattered Caches

Infinispan stores cache entries across a subset of nodes. By default Infinispan assigns a primary owner and a backup owner to each cache entry in scattered caches. Infinispan assigns primary owners in the same way as with distributed caches, while backup owners are always the nodes that initiate the write operations. Infinispan requests read operations from at least one owner node to ensure it returns the correct value.

#### 1.4.1. Cache Mode Comparison

The cache mode that you should choose depends on the qualities and guarantees you need for your data.

The following table summarizes the primary differences between cache modes:

Simple Local Invalidation Replicated Distributed Scattered

Clustered

No

No

Yes

Yes

Yes

Yes

Highest
(local)

High
(local)

High
(local)

High
(local)

Medium
(owners)

Medium
(primary)

Write performance

Highest
(local)

High
(local)

Low
(all nodes, no data)

Lowest
(all nodes)

Medium
(owner nodes)

Higher
(single RPC)

Capacity

Single node

Single node

Single node

Smallest node

Cluster
(sum_(i=1)^"nodes""node_capacity")/"owners"

Cluster
(sum_(i=1)^"nodes""node_capacity")/"2"

Availability

Single node

Single node

Single node

All nodes

Owner nodes

Owner nodes

Features

No TX, persistence, indexing

All

All

All

All

No TX

## 2. Local Caches

While Infinispan is particularly interesting in clustered mode, it also offers a very capable local mode. In this mode, it acts as a simple, in-memory data cache similar to a `ConcurrentHashMap`.

But why would one use a local cache rather than a map? Caches offer a lot of features over and above a simple map, including write-through and write-behind to a persistent store, eviction of entries to prevent running out of memory, and expiration.

Infinispan’s `Cache` interface extends JDK’s `ConcurrentMap` — making migration from a map to Infinispan trivial.

Infinispan caches also support transactions, either integrating with an existing transaction manager or running a separate one. Local caches transactions have two choices:

1. When to lock? Pessimistic locking locks keys on a write operation or when the user calls `AdvancedCache.lock(keys)` explicitly. Optimistic locking only locks keys during the transaction commit, and instead it throws a `WriteSkewCheckException` at commit time, if another transaction modified the same keys after the current transaction read them.

### 2.1. Simple Caches

Traditional local caches use the same architecture as clustered caches, i.e. they use the interceptor stack. That way a lot of the implementation can be reused. However, if the advanced features are not needed and performance is more important, the interceptor stack can be stripped away and simple cache can be used.

So, which features are stripped away? From the configuration perspective, simple cache does not support:

• transactions and invocation batching

• persistence (cache stores and loaders)

• custom interceptors (there’s no interceptor stack!)

• indexing

• transcoding

• store as binary (which is hardly useful for local caches)

From the API perspective these features throw an exception:

• Distributed Executors Framework

So, what’s left?

• basic map-like API

• cache listeners (local ones)

• expiration

• eviction

• security

• JMX access

• statistics (though for max performance it is recommended to switch this off using statistics-available=false)

Declarative configuration
``````<local-cache name="mySimpleCache" simple-cache="true">
<!-- expiration, eviction, security... -->
</local-cache>``````
Programmatic configuration
``````DefaultCacheManager cm = getCacheManager();
ConfigurationBuilder builder = new ConfigurationBuilder().simpleCache(true);
cm.defineConfiguration("mySimpleCache", builder.build());
Cache cache = cm.getCache("mySimpleCache");``````

Simple cache checks against features it does not support, if you configure it to use e.g. transactions, configuration validation will throw an exception.

## 3. Clustered Caches

Clustered caches store data across multiple Infinispan nodes using JGroups technology as the transport layer to pass data across the network.

### 3.1. Invalidation Mode

You can use Infinispan in invalidation mode to optimize systems that perform high volumes of read operations. A good example is to use invalidation to prevent lots of database writes when state changes occur.

This cache mode only makes sense if you have another, permanent store for your data such as a database and are only using Infinispan as an optimization in a read-heavy system, to prevent hitting the database for every read. If a cache is configured for invalidation, every time data is changed in a cache, other caches in the cluster receive a message informing them that their data is now stale and should be removed from memory and from any local store.

Figure 1. Invalidation mode

Sometimes the application reads a value from the external store and wants to write it to the local cache, without removing it from the other nodes. To do this, it must call `Cache.putForExternalRead(key, value)` instead of `Cache.put(key, value)`.

Invalidation mode can be used with a shared cache store. A write operation will both update the shared store, and it would remove the stale values from the other nodes' memory. The benefit of this is twofold: network traffic is minimized as invalidation messages are very small compared to replicating the entire value, and also other caches in the cluster look up modified data in a lazy manner, only when needed.

 Never use invalidation mode with a local store. The invalidation message will not remove entries in the local store, and some nodes will keep seeing the stale value.

An invalidation cache can also be configured with a special cache loader, `ClusterLoader`. When `ClusterLoader` is enabled, read operations that do not find the key on the local node will request it from all the other nodes first, and store it in memory locally. In certain situation it will store stale values, so only use it if you have a high tolerance for stale values.

Invalidation mode can be synchronous or asynchronous. When synchronous, a write blocks until all nodes in the cluster have evicted the stale value. When asynchronous, the originator broadcasts invalidation messages but doesn’t wait for responses. That means other nodes still see the stale value for a while after the write completed on the originator.

Transactions can be used to batch the invalidation messages. Transactions acquire the key lock on the primary owner. To find more about how primary owners are assigned, please read the Key Ownership section.

• With pessimistic locking, each write triggers a lock message, which is broadcast to all the nodes. During transaction commit, the originator broadcasts a one-phase prepare message (optionally fire-and-forget) which invalidates all affected keys and releases the locks.

• With optimistic locking, the originator broadcasts a prepare message, a commit message, and an unlock message (optional). Either the one-phase prepare or the unlock message is fire-and-forget, and the last message always releases the locks.

### 3.2. Replicated Caches

Entries written to a replicated cache on any node will be replicated to all other nodes in the cluster, and can be retrieved locally from any node. Replicated mode provides a quick and easy way to share state across a cluster, however replication practically only performs well in small clusters (under 10 nodes), due to the number of messages needed for a write scaling linearly with the cluster size. Infinispan can be configured to use UDP multicast, which mitigates this problem to some degree.

Each key has a primary owner, which serializes data container updates in order to provide consistency. To find more about how primary owners are assigned, please read the Key Ownership section.

Figure 2. Replicated mode

Replicated mode can be synchronous or asynchronous.

• Synchronous replication blocks the caller (e.g. on a `cache.put(key, value)`) until the modifications have been replicated successfully to all the nodes in the cluster.

• Asynchronous replication performs replication in the background, and write operations return immediately. Asynchronous replication is not recommended, because communication errors, or errors that happen on remote nodes are not reported to the caller.

If transactions are enabled, write operations are not replicated through the primary owner.

• With pessimistic locking, each write triggers a lock message, which is broadcast to all the nodes. During transaction commit, the originator broadcasts a one-phase prepare message and an unlock message (optional). Either the one-phase prepare or the unlock message is fire-and-forget.

• With optimistic locking, the originator broadcasts a prepare message, a commit message, and an unlock message (optional). Again, either the one-phase prepare or the unlock message is fire-and-forget.

### 3.3. Distributed Caches

Distribution tries to keep a fixed number of copies of any entry in the cache, configured as `numOwners`. This allows the cache to scale linearly, storing more data as nodes are added to the cluster.

As nodes join and leave the cluster, there will be times when a key has more or less than `numOwners` copies. In particular, if `numOwners` nodes leave in quick succession, some entries will be lost, so we say that a distributed cache tolerates `numOwners - 1` node failures.

The number of copies represents a trade-off between performance and durability of data. The more copies you maintain, the lower performance will be, but also the lower the risk of losing data due to server or network failures. Regardless of how many copies are maintained, distribution still scales linearly, and this is key to Infinispan’s scalability.

The owners of a key are split into one primary owner, which coordinates writes to the key, and zero or more backup owners. To find more about how primary and backup owners are assigned, please read the Key Ownership section.

Figure 3. Distributed mode

A read operation will request the value from the primary owner, but if it doesn’t respond in a reasonable amount of time, we request the value from the backup owners as well. (The `infinispan.stagger.delay` system property, in milliseconds, controls the delay between requests.) A read operation may require `0` messages if the key is present in the local cache, or up to `2 * numOwners` messages if all the owners are slow.

A write operation will also result in at most `2 * numOwners` messages: one message from the originator to the primary owner, `numOwners - 1` messages from the primary to the backups, and the corresponding ACK messages.

 Cache topology changes may cause retries and additional messages, both for reads and for writes.

Just as replicated mode, distributed mode can also be synchronous or asynchronous. And as in replicated mode, asynchronous replication is not recommended because it can lose updates. In addition to losing updates, asynchronous distributed caches can also see a stale value when a thread writes to a key and then immediately reads the same key.

Transactional distributed caches use the same kinds of messages as transactional replicated caches, except lock/prepare/commit/unlock messages are sent only to the affected nodes (all the nodes that own at least one key affected by the transaction) instead of being broadcast to all the nodes in the cluster. As an optimization, if the transaction writes to a single key and the originator is the primary owner of the key, lock messages are not replicated.

Even with synchronous replication, distributed caches are not linearizable. (For transactional caches, we say they do not support serialization/snapshot isolation.) We can have one thread doing a single put:

``````cache.get(k) -> v1
cache.put(k, v2)
cache.get(k) -> v2``````

But another thread might see the values in a different order:

``````cache.get(k) -> v2
cache.get(k) -> v1``````

The reason is that read can return the value from any owner, depending on how fast the primary owner replies. The write is not atomic across all the owners — in fact, the primary commits the update only after it receives a confirmation from the backup. While the primary is waiting for the confirmation message from the backup, reads from the backup will see the new value, but reads from the primary will see the old one.

#### 3.3.2. Key Ownership

Distributed caches split entries into a fixed number of segments and assign each segment to a list of owner nodes. Replicated caches do the same, with the exception that every node is an owner.

The first node in the list of owners is the primary owner. The other nodes in the list are backup owners. When the cache topology changes, because a node joins or leaves the cluster, the segment ownership table is broadcast to every node. This allows nodes to locate keys without making multicast requests or maintaining metadata for each key.

The `numSegments` property configures the number of segments available. However, the number of segments cannot change unless the cluster is restarted.

Likewise the key-to-segment mapping cannot change. Keys must always map to the same segments regardless of cluster topology changes. It is important that the key-to-segment mapping evenly distributes the number of segments allocated to each node while minimizing the number of segments that must move when the cluster topology changes.

You can customize the key-to-segment mapping by configuring a KeyPartitioner or by using the Grouping API.

However, Infinispan provides the following implementations:

SyncConsistentHashFactory

Uses an algorithm based on consistent hashing. Selected by default when server hinting is disabled.

This implementation always assigns keys to the same nodes in every cache as long as the cluster is symmetric. In other words, all caches run on all nodes. This implementation does have some negative points in that the load distribution is slightly uneven. It also moves more segments than strictly necessary on a join or leave.

TopologyAwareSyncConsistentHashFactory

Similar to `SyncConsistentHashFactory`, but adapted for Server Hinting. Selected by default when server hinting is enabled.

DefaultConsistentHashFactory

Achieves a more even distribution than `SyncConsistentHashFactory`, but with one disadvantage. The order in which nodes join the cluster determines which nodes own which segments. As a result, keys might be assigned to different nodes in different caches.

Was the default from version 5.2 to version 8.1 with server hinting disabled.

TopologyAwareConsistentHashFactory

Similar to DefaultConsistentHashFactory, but adapted for Server Hinting.

Was the default from version 5.2 to version 8.1 with server hinting enabled.

ReplicatedConsistentHashFactory

Used internally to implement replicated caches. You should never explicitly select this algorithm in a distributed cache.

##### Capacity Factors

Capacity factors allocate segment-to-node mappings based on resources available to nodes.

To configure capacity factors, you specify any non-negative number and the Infinispan hashing algorithm assigns each node a load weighted by its capacity factor (both as a primary owner and as a backup owner).

For example, nodeA has 2x the memory available than nodeB in the same Infinispan cluster. In this case, setting `capacityFactor` to a value of `2` configures Infinispan to allocate 2x the number of segments to nodeA.

Setting a capacity factor of `0` is possible but is recommended only in cases where nodes are not joined to the cluster long enough to be useful data owners.

#### 3.3.3. Zero Capacity Node

You might need to configure a whole node where the capacity factor is `0` for every cache, user defined caches and internal caches. When defining a zero capacity node, the node won’t hold any data. This is how you declare a zero capacity node:

``<cache-container zero-capacity-node="true" />``
``new GlobalConfigurationBuilder().zeroCapacityNode(true);``

However, note that this will be true for distributed caches only. If you are using replicated caches, the node will still keep a copy of the value. Use only distributed caches to make the best use of this feature.

#### 3.3.4. Hashing Configuration

This is how you configure hashing declaratively, via XML:

``<distributed-cache name="distributedCache" owners="2" segments="100" capacity-factor="2" />``

And this is how you can configure it programmatically, in Java:

``````Configuration c = new ConfigurationBuilder()
.clustering()
.cacheMode(CacheMode.DIST_SYNC)
.hash()
.numOwners(2)
.numSegments(100)
.capacityFactor(2)
.build();``````

#### 3.3.5. Initial cluster size

Infinispan’s very dynamic nature in handling topology changes (i.e. nodes being added / removed at runtime) means that, normally, a node doesn’t wait for the presence of other nodes before starting. While this is very flexible, it might not be suitable for applications which require a specific number of nodes to join the cluster before caches are started. For this reason, you can specify how many nodes should have joined the cluster before proceeding with cache initialization. To do this, use the `initialClusterSize` and `initialClusterTimeout` transport properties. The declarative XML configuration:

``<transport initial-cluster-size="4" initial-cluster-timeout="30000" />``

The programmatic Java configuration:

``````GlobalConfiguration global = new GlobalConfigurationBuilder()
.transport()
.initialClusterSize(4)
.initialClusterTimeout(30000, TimeUnit.MILLISECONDS)
.build();``````

The above configuration will wait for 4 nodes to join the cluster before initialization. If the initial nodes do not appear within the specified timeout, the cache manager will fail to start.

#### 3.3.6. L1 Caching

When L1 is enabled, a node will keep the result of remote reads locally for a short period of time (configurable, 10 minutes by default), and repeated lookups will return the local L1 value instead of asking the owners again.

Figure 4. L1 caching

L1 caching is not free though. Enabling it comes at a cost, and this cost is that every entry update must broadcast an invalidation message to all the nodes. L1 entries can be evicted just like any other entry when the the cache is configured with a maximum size. Enabling L1 will improve performance for repeated reads of non-local keys, but it will slow down writes and it will increase memory consumption to some degree.

Is L1 caching right for you? The correct approach is to benchmark your application with and without L1 enabled and see what works best for your access pattern.

#### 3.3.7. Server Hinting

The following topology hints can be specified:

Machine

This is probably the most useful, when multiple JVM instances run on the same node, or even when multiple virtual machines run on the same physical machine.

Rack

In larger clusters, nodes located on the same rack are more likely to experience a hardware or network failure at the same time.

Site

Some clusters may have nodes in multiple physical locations for extra resilience. Note that Cross site replication is another alternative for clusters that need to span two or more data centres.

All of the above are optional. When provided, the distribution algorithm will try to spread the ownership of each segment across as many sites, racks, and machines (in this order) as possible.

##### Configuration

The hints are configured at transport level:

``````<transport
cluster="MyCluster"
machine="LinuxServer01"
rack="Rack01"
site="US-WestCoast" />``````

#### 3.3.8. Key affinity service

In a distributed cache, a key is allocated to a list of nodes with an opaque algorithm. There is no easy way to reverse the computation and generate a key that maps to a particular node. However, we can generate a sequence of (pseudo-)random keys, see what their primary owner is, and hand them out to the application when it needs a key mapping to a particular node.

##### API

Following code snippet depicts how a reference to this service can be obtained and used.

``````// 1. Obtain a reference to a cache
Cache cache = ...

// 2. Create the affinity service
KeyAffinityService keyAffinityService = KeyAffinityServiceFactory.newLocalKeyAffinityService(
cache,
new RndKeyGenerator(),
100);

// 3. Obtain a key for which the local node is the primary owner

// 4. Insert the key in the cache
cache.put(localKey, "yourValue");``````

The service is started at step 2: after this point it uses the supplied Executor to generate and queue keys. At step 3, we obtain a key from the service, and at step 4 we use it.

##### Lifecycle

`KeyAffinityService` extends `Lifecycle`, which allows stopping and (re)starting it:

``````public interface Lifecycle {
void start();
void stop();
}``````

The service is instantiated through `KeyAffinityServiceFactory`. All the factory methods have an `Executor` parameter, that is used for asynchronous key generation (so that it won’t happen in the caller’s thread). It is the user’s responsibility to handle the shutdown of this `Executor`.

The `KeyAffinityService`, once started, needs to be explicitly stopped. This stops the background key generation and releases other held resources.

The only situation in which `KeyAffinityService` stops by itself is when the cache manager with which it was registered is shutdown.

##### Topology changes

When the cache topology changes (i.e. nodes join or leave the cluster), the ownership of the keys generated by the `KeyAffinityService` might change. The key affinity service keep tracks of these topology changes and doesn’t return keys that would currently map to a different node, but it won’t do anything about keys generated earlier.

As such, applications should treat `KeyAffinityService` purely as an optimization, and they should not rely on the location of a generated key for correctness.

In particular, applications should not rely on keys generated by `KeyAffinityService` for the same address to always be located together. Collocation of keys is only provided by the Grouping API.

##### The Grouping API

Complementary to Key affinity service, the grouping API allows you to co-locate a group of entries on the same nodes, but without being able to select the actual nodes.

##### How does it work?

By default, the segment of a key is computed using the key’s `hashCode()`. If you use the grouping API, Infinispan will compute the segment of the group and use that as the segment of the key. See the Key Ownership section for more details on how segments are then mapped to nodes.

When the group API is in use, it is important that every node can still compute the owners of every key without contacting other nodes. For this reason, the group cannot be specified manually. The group can either be intrinsic to the entry (generated by the key class) or extrinsic (generated by an external function).

##### How do I use the grouping API?

First, you must enable groups. If you are configuring Infinispan programmatically, then call:

``````Configuration c = new ConfigurationBuilder()
.clustering().hash().groups().enabled()
.build();``````

Or, if you are using XML:

``````<distributed-cache>
<groups enabled="true"/>
</distributed-cache>``````

If you have control of the key class (you can alter the class definition, it’s not part of an unmodifiable library), then we recommend using an intrinsic group. The intrinsic group is specified by adding the `@Group` annotation to a method. Let’s take a look at an example:

``````class User {
...
String office;
...

public int hashCode() {
// Defines the hash for the key, normally used to determine location
...
}

// Override the location by specifying a group
// All keys in the same group end up with the same owners
@Group
public String getOffice() {
return office;
}
}
}``````
 The group method must return a `String`

If you don’t have control over the key class, or the determination of the group is an orthogonal concern to the key class, we recommend using an extrinsic group. An extrinsic group is specified by implementing the `Grouper` interface.

``````public interface Grouper<T> {
String computeGroup(T key, String group);

Class<T> getKeyType();
}``````

If multiple `Grouper` classes are configured for the same key type, all of them will be called, receiving the value computed by the previous one. If the key class also has a `@Group` annotation, the first `Grouper` will receive the group computed by the annotated method. This allows you even greater control over the group when using an intrinsic group. Let’s take a look at an example `Grouper` implementation:

``````public class KXGrouper implements Grouper<String> {

// The pattern requires a String key, of length 2, where the first character is
// "k" and the second character is a digit. We take that digit, and perform
// modular arithmetic on it to assign it to group "0" or group "1".

#### 6.1.1. Default JGroups Stacks

Default JGroups stacks are included in `infinispan-core.jar` and on the classpath. You can locate the default JGroups stacks in the `default-configs` directory.

File name Stack name Description

`default-jgroups-udp.xml`

`udp`

Uses UDP for transport and UDP multicast for discovery. Suitable for larger clusters (over 100 nodes) or if you are using replicated caches or invalidation mode. Minimizes the number of open sockets.

`default-jgroups-tcp.xml`

`tcp`

Uses TCP for transport and the `MPING` protocol for discovery, which uses `UDP` multicast. Suitable for smaller clusters (under 100 nodes) only if you are using distributed caches because TCP is more efficient than UDP as a point-to-point protocol.

`default-jgroups-ec2.xml`

`ec2`

Uses TCP for transport and `S3_PING` for discovery. Suitable for Amazon EC2 nodes where UDP multicast is not available.

`default-jgroups-kubernetes.xml`

`kubernetes`

Uses TCP for transport and `DNS_PING` for discovery. Suitable for Kubernetes and Red Hat OpenShift nodes where UDP multicast is not always available.

`default-jgroups-google.xml`

`google`

Uses TCP for transport and `GOOGLE_PING2` for discovery. Suitable for Google Cloud Platform nodes where UDP multicast is not available.

`default-jgroups-azure.xml`

`azure`

Uses TCP for transport and `AZURE_PING` for discovery. Suitable for Microsoft Azure nodes where UDP multicast is not available.

Reference

### 6.2. Using Inline JGroups Stacks

Custom JGroups stacks can help you optimize network performance for Infinispan clusters compared to using the default stacks.

Procedure
• Embed your custom JGroups stack definitions in `infinispan.xml` as in the following example:

``````<infinispan> (1)
<jgroups> (2)
<stack name="prod"> (3)
<TCP bind_port="7800" port_range="30" recv_buf_size="20000000" send_buf_size="640000"/>
mcast_addr="${jgroups.mping.mcast_addr:228.2.4.6}" mcast_port="${jgroups.mping.mcast_port:43366}"
num_discovery_runs="3"
ip_ttl="${jgroups.udp.ip_ttl:2}"/> <MERGE3 /> <FD_SOCK /> <FD_ALL timeout="3000" interval="1000" timeout_check_interval="1000" /> <VERIFY_SUSPECT timeout="1000" /> <pbcast.NAKACK2 use_mcast_xmit="false" xmit_interval="100" xmit_table_num_rows="50" xmit_table_msgs_per_row="1024" xmit_table_max_compaction_time="30000" /> <UNICAST3 xmit_interval="100" xmit_table_num_rows="50" xmit_table_msgs_per_row="1024" xmit_table_max_compaction_time="30000" /> <pbcast.STABLE stability_delay="200" desired_avg_gossip="2000" max_bytes="1M" /> <pbcast.GMS print_local_addr="false" join_timeout="${jgroups.join_timeout:2000}" />
<UFC max_credits="4m" min_threshold="0.40" />
<MFC max_credits="4m" min_threshold="0.40" />
<FRAG3 />
</stack>
</jgroups>
<cache-container default-cache="replicatedCache"> (4)
<transport stack="prod" /> (5)
...
</cache-container>
</infinispan>``````
 1 root element of `infinispan.xml`. 2 contains JGroups stack definitions. 3 defines a JGroups stack named "prod". 4 configures a Infinispan Cache Manager and names the "replicatedCache" cache definition as the default. 5 uses the "prod" JGroups stack for cluster transport.
 Use inheritance with inline JGroups stacks to tune and customize specific transport properties.

### 6.3. Adjusting and Tuning JGroups Stacks

Use inheritance to combine, extend, remove, and replace specific properties in the default JGroups stacks or custom configurations.

Procedure
1. Add a new JGroups stack declaration.

2. Name a parent stack with the `extends` attribute.

 Use the default JGroups stacks as parents. For example, `extends="tcp"` to tunes the default TCP stack.
3. Modify transport properties with the `stack.combine` attribute.

#### 6.3.1. Stack Combine Attribute

`stack.combine` modifies inherited JGroups properties.

`stack.position` identifies protocols to modify. If you do not specify `stack.position`, Infinispan defaults to the same protocol as the inherited configuration, which resets all non-specified attributes to the default values.

Value Description

`COMBINE`

Overrides existing protocol attributes.

`REPLACE`

Replaces existing protocols.

`INSERT_AFTER`

Inserts protocols into the JGroups stack.

`REMOVE`

Removes protocols from the inherited configuration.

For example, evaluate a Gossip router for cluster discovery using a TCP stack configuration named "prod":

``````<jgroups>
...
<stack name="gossip-prod" extends="prod"> (1)
<TCPGOSSIP initial_hosts="${jgroups.tunnel.gossip_router_hosts:localhost[12001]}" stack.combine="REPLACE" stack.position="MPING" /> (2) <FD_SOCK stack.combine="REMOVE"/> (3) <VERIFY_SUSPECT timeout="2000"/> (4) <SYM_ENCRYPT sym_algorithm="AES" key_store_name="defaultStore.keystore" store_password="changeit" alias="myKey" stack.combine="INSERT_AFTER" stack.position="pbcast.NAKACK2" /> (5) </stack> ... </jgroups>``````  1 creates a new stack named "gossip-prod" that inherits from "prod". 2 uses `TCPGOSSIP` discovery instead of `MPING`. 3 removes `FD_SOCK` from the "gossip-prod" stack. 4 increases the `VERIFY_SUSPECT` timeout. 5 adds `SYM_ENCRYPT` for cluster security to the stack after the `pbcast.NAKACK2` protocol. ### 6.4. Using JGroups Stacks in External Files You can use custom JGroups transport configuration from external files. Infinispan looks for JGroups configuration files on your classpath first and then for absolute path names. Declaratively • Specify your JGroups transport configuration with the `stack-file` element. ``````<infinispan> <jgroups> <stack-file name="prod-tcp" path="prod-jgroups-tcp.xml"/> (1) </jgroups> <cache-container default-cache="replicatedCache"> <transport stack="prod-tcp" /> (2) <replicated-cache name="replicatedCache"/> </cache-container> ... </infinispan>``````  1 adds the "prod-jgroups-tcp.xml" stack definition. 2 configures Infinispan cluster to use the stack. Programmatically • Specify your JGroups transport configuration with the `addProperty()` method. ``````GlobalConfiguration globalConfig = new GlobalConfigurationBuilder().transport() .defaultTransport() .clusterName("prod-cluster") .addProperty("configurationFile", "prod-jgroups-tcp.xml") (1) .build();``````  1 adds the "prod-jgroups-tcp.xml" stack definition as the default for the cluster transport. ### 6.5. Tuning JGroups Stacks with System Properties Pass system properties to the JVM at startup to tune JGroups stacks. For example, to change the `TCP` port and IP address do the following: ``$ java -cp ... -Djgroups.tcp.port=1234 -Djgroups.tcp.address=192.0.2.0``

#### 6.5.1. System Properties for Default JGroups Stacks

Use system properties with default JGroups stacks.

Common Properties

The following system properties apply to all JGroups stacks, including `default-jgroups-udp.xml` and `default-jgroups-tcp.xml`:

System Property Description Default Value Required/Optional

`jgroups.bind.address`

`SITE_LOCAL`

Optional

`jgroups.bind.port`

Bind port for the socket.

`7800`

Optional

`jgroups.mcast_addr`

IP address for multicast, both discovery and inter-cluster communication. The IP address must be a valid "class D" address that is suitable for IP multicast.

`228.6.7.8`

Optional

`jgroups.mcast_port`

Port for the multicast socket.

`46655`

Optional

`jgroups.ip_ttl`

Time-to-live (TTL) for IP multicast packets. The value defines the number of network hops a packet can make before it is dropped.

2

Optional

`jgroups.thread_pool.min_threads`

0

Optional

`jgroups.thread_pool.max_threads`

200

Optional

`jgroups.join_timeout`

Maximum number of milliseconds to wait for join requests to succeed.

2000

Optional

Amazon EC3

The following system properties apply to `default-jgroups-ec2.xml`:

System Property Description Default Value Required/Optional

`jgroups.s3.access_key`

Amazon S3 access key for an S3 bucket.

No default value.

Optional

`jgroups.s3.secret_access_key`

Amazon S3 secret key used for an S3 bucket.

No default value.

Optional

`jgroups.s3.bucket`

Name of the Amazon S3 bucket. The name must exist and be unique.

No default value.

Optional

Kubernetes

The following system properties apply to `default-jgroups-kubernetes.xml`:

System Property Description Default Value Required/Optional

`jgroups.dns.query`

Sets the DNS record that returns cluster members.

N/A

Required if you do not set the `dns_query` parameter.

The following system properties apply to `default-jgroups-google.xml`:

System Property Description Default Value Required/Optional

`jgroups.google.bucket_name`

Name of the Google Compute Engine bucket. The name must exist and be unique.

N/A

Required if you do not set the `dns_query` parameter.

Reference

### 6.6. Using Custom JChannels

Construct custom JGroups JChannels as in the following example:

``````GlobalConfigurationBuilder global = new GlobalConfigurationBuilder();
JChannel jchannel = new JChannel();
// Configure the jchannel to your needs.
JGroupsTransport transport = new JGroupsTransport(jchannel);
global.transport().transport(transport);
new DefaultCacheManager(global.build());``````
 Infinispan cannot use custom JChannels that are already connected.
Reference

JGroups JChannel

## 7. Configuring Cluster Discovery

Running Infinispan on hosted services requires using discovery mechanisms that are adapted to network constraints that individual cloud providers impose. For instance, Amazon EC2 does not allow UDP multicast.

Infinispan can use the following cloud discovery mechanisms:

• Generic discovery protocols (`TCPPING` and `TCPGOSSIP`)

• JGroups PING protocols (`KUBE_PING` and `DNS_PING`)

• Cloud-specific PING protocols

 Embedded Infinispan requires cloud provider dependencies.

### 7.1. TCPPING

`TCPPING` is a generic JGroups discovery mechanism that uses a static list of IP addresses for cluster members.

To use `TCPPING`, you must add the list of static IP addresses to the JGroups configuration file for each Infinispan node. However, the drawback to `TCPPING` is that it does not allow nodes to dynamically join Infinispan clusters.

TCPPING configuration example
``````<config>
<TCP bind_port="7800" />
<TCPPING timeout="3000"
...
...
</config>``````

### 7.3. DNS_PING

JGroups `DNS_PING` queries DNS servers to discover Infinispan cluster members in Kubernetes environments such as OKD and Red Hat OpenShift.

DNS_PING configuration example
``````<stack name="dns-ping">
...
<dns.DNS_PING
dns_query="myservice.myproject.svc.cluster.local" />
...
</stack>``````
Reference

### 7.4. KUBE_PING

JGroups `Kube_PING` uses a Kubernetes API to discover Infinispan cluster members in environments such as OKD and Red Hat OpenShift.

KUBE_PING configuration example
``````<config>
<TCP bind_addr="${match-interface:eth.*}" /> <kubernetes.KUBE_PING /> ... ... </config>`````` KUBE_PING configuration requirements • Your `KUBE_PING` configuration must bind the JGroups stack to the `eth0` network interface. Docker containers use `eth0` for communication. • `KUBE_PING` uses environment variables inside containers for configuration. The `KUBERNETES_NAMESPACE` environment variable must specify a valid namespace. You can either hardcode it or populate it via the Kubernetes Downward API. • `KUBE_PING` requires additional privileges on Red Hat OpenShift. Assuming that `oc project -q` returns the current namespace and `default` is the service account name, you can run: ``$ oc policy add-role-to-user view system:serviceaccount:$(oc project -q):default -n$(oc project -q)``
Reference

### 7.5. NATIVE_S3_PING

On Amazon Web Service (AWS), use the `S3_PING` protocol for discovery.

You can configure JGroups to use shared storage to exchange the details of Infinispan nodes. `NATIVE_S3_PING` allows Amazon S3 as the shared storage but requires both Amazon S3 and EC2 subscriptions.

NATIVE_S3_PING configuration example
``````<config>
<TCP bind_port="7800" />
<org.jgroups.aws.s3.NATIVE_S3_PING
region_name="replace this with your region (e.g. eu-west-1)"
bucket_name="replace this with your bucket name"
bucket_prefix="replace this with a prefix to use for entries in the bucket (optional)" />
</config>``````
NATIVE_S3_PING dependencies for embedded Infinispan
``````<dependency>
<groupId>org.jgroups.aws.s3</groupId>
<artifactId>native-s3-ping</artifactId>
<version>${version.jgroups.native_s3_ping}</version> </dependency>`````` ### 7.6. JDBC_PING `JDBC_PING` uses JDBC connections to shared databases, such as Amazon RDS on EC2, to store information about Infinispan nodes. Reference JDBC_PING Wiki ### 7.7. AZURE_PING On Microsoft Azure, use a generic discovery protocol or `AZURE_PING`, which uses shared Azure Blob Storage to store discovery information. AZURE_PING configuration example ``````<azure.AZURE_PING storage_account_name="replace this with your account name" storage_access_key="replace this with your access key" container="replace this with your container name" />`````` AZURE_PING dependencies for embedded Infinispan ``````<dependency> <groupId>org.jgroups.azure</groupId> <artifactId>jgroups-azure</artifactId> <version>${version.jgroups.azure}</version>
</dependency>``````

On Google Compute Engine (GCE), use a generic discovery protocol or `GOOGLE2_PING`, which uses Google Cloud Storage (GCS) to store information about the cluster members.

``<org.jgroups.protocols.google.GOOGLE_PING2 location="${jgroups.google.bucket_name}" />`` GOOGLE2_PING dependencies for embedded Infinispan ``````<dependency> <groupId>org.jgroups.google</groupId> <artifactId>jgroups-google</artifactId> <version>${version.jgroups.google}</version>
</dependency>``````

## 8. Configuring and Cleaning the Data Container

Configure Infinispan to evict and expire cache entries, keeping only recently active entries in memory and protecting the size of the data container.

### 8.1. Eviction and Expiration Overview

Eviction and expiration are two strategies that have similar results in that they remove old, unused entries. Although eviction and expiration are similar, they have some important differences that you should take into account when planning your configuration.

• Eviction prevents Infinispan from exceeding the maximum size of the data container. Infinispan performs eviction when you add entries to the cache.

• Expiration limits the amount of time entries can exist. Infinispan uses a scheduler to periodically remove expired entries. Entries that are expired but not yet removed are immediately removed on access; in this case `get()` calls for expired entries return "null" values.

• Eviction is local to Infinispan nodes.

• Expiration takes place across Infinispan clusters.

• You can use eviction and expiration together or independently of each other.

• You can configure eviction and expiration declaratively in `infinispan.xml` to apply cache-wide defaults for entries.

• You can explicitly define expiration settings for specific entries but you cannot define eviction on a per-entry basis.

• You can manually evict entries and manually trigger expiration.

Data containers

In the context of eviction and expiration, the term "data container" refers to where in-memory data is stored, which is either on or off the JVM heap.

### 8.2. Eviction

Eviction provides a way to manage how much memory Infinispan uses.

Infinispan lets you configure the maximum size of the data container. Eviction removes entries from the cache to ensure that Infinispan does not exceed that maximum size.

 Eviction removes entries from memory but not from persistent cache stores.

#### 8.2.1. How Eviction Works

Infinispan eviction removes entries from the data container to make space when adding new entries.

 To prevent data loss, you should always configure a persistent cache store if you enable eviction.

Infinispan eviction relies on two configurations:

• Size of the data container.

• Eviction strategy.

Calculating data container size

You configure the maximum size of the data container and specify if Infinispan stores cache entries as:

• Object in the Java heap.

• Binary `byte[]` in the Java heap.

• Bytes in native memory (off-heap).

Storage type Size of the data container is calculated as:

Object

Number of entries.

Binary

Number of entries, if the eviction type is `COUNT`.
Amount of memory, in bytes, if the eviction type is `MEMORY`.

Off-heap

Number of entries, if the eviction type is `COUNT`.
Amount of memory, in bytes, if the eviction type is `MEMORY`.

 When using `MEMORY`, Infinispan can determine only an approximate size of data containers, which is optimized for the HotSpot JVM. When using `MEMORY` with off-heap storage, the calculation is a closer approximation than on heap.
Evicting cache entries

When an entry is added or modified in the data container, Infinispan compares the current eviction size to the maximum size. If the current size exceeds the maximum, Infinispan evicts entries.

Eviction happens immediately in the thread that adds an entry that exceeds the maximum size.

For example, consider the following configuration:

```<memory>
<object size="50" />
</memory>```

In this case, entries are stored as objects and the data container has a maximum size of 50 entries.

If 50 entries are in the data container, and a `put()` request attempts to create a new entry, Infinispan performs eviction.

Eviction strategies

Strategies control how Infinispan performs eviction. You can either perform eviction manually or configure Infinispan to do one of the following:

• Remove old entries to make space for new ones.

• Throw `ContainerFullException` and prevent new entries from being created.

The exception eviction strategy works only with transactional caches that use 2 phase commits; not with 1 phase commits or synchronization optimizations.

 Infinispan includes the Caffeine caching library that implements a variation of the Least Frequently Used (LFU) cache replacement algorithm known as TinyLFU. For off-heap storage, Infinispan uses a custom implementation of the Least Recently Used (LRU) algorithm.
References

#### 8.2.2. Eviction Examples

You configure eviction in `infinispan.xml` as part of your cache definition.

Default memory configuration

Eviction is not enabled, which is the default configuration. Infinispan stores cache entries as objects in the data container.

``<memory />``
Passivation with eviction

Passivation persists data to cache stores when Infinispan evicts entries. You should always enable eviction if you enable passivation.

``````<persistence passivation="true">
...
</persistence>

<memory />``````
Manual eviction

Infinispan stores cache entries as objects. Eviction is not enabled but performed manually using the `evict()` method.

``````<memory>
<object strategy="MANUAL" />
</memory>``````
Object storage with eviction

Infinispan stores cache entries as objects. Eviction happens when there are 100 entries in the data container and Infinispan gets a request to create a new entry:

``````<memory>
<object size="100" />
</memory>``````
Binary storage with memory-based eviction

Infinispan stores cache entries as bytes. Eviction happens when the size of the data container reaches 100 bytes and Infinispan gets a request to create a new entry:

``````<memory>
<binary size="100" eviction="MEMORY"/>
</memory>``````
Off-heap storage with count-based eviction

Infinispan stores cache entries as bytes in native memory. Eviction happens when there are 100 entries in the data container and Infinispan gets a request to create a new entry:

``````<memory>
<off-heap size="100" />
</memory>``````
Off-heap storage with the exception strategy

Infinispan stores cache entries as bytes in native memory. When there are 100 entries in the data container, and Infinispan gets a request to create a new entry, it throws an exception and does not allow the new entry:

``````<memory>
<off-heap size="100" strategy="EXCEPTION" />
</memory>``````

#### 8.2.3. Custom Classes with Memory-Based Eviction

You must use binary or off-heap storage memory based eviction, as in the following examples:

Declarative configuration
``````<!-- Enable memory based eviction with 1 GB/> -->
<memory>
<binary size="1000000000" eviction="MEMORY"/>
</memory>``````
Programmatic configuration
``````Configuration c = new ConfigurationBuilder()
.memory()
.storageType(StorageType.BINARY)
.evictionType(EvictionType.MEMORY)
.size(1_000_000_000)
.build();``````

### 8.3. Expiration

Expiration removes entries from caches when they reach one of the following time limits:

Lifespan

Sets the maximum amount of time that entries can exist.

Maximum idle

Specifies how long entries can remain idle. If operations do not occur for entries, they become idle.

 Maximum idle expiration does not currently support cache configurations with persistent cache stores. When using expiration with an exception-based eviction policy, entries that are expired but not yet removed from the cache count towards the size of the data container.

#### 8.3.1. How Expiration Works

When you configure expiration, Infinispan stores keys with metadata that determines when entries expire.

• Lifespan uses a `creation` timestamp and the value for the `lifespan` configuration property.

• Maximum idle uses a `last used` timestamp and the value for the `max-idle` configuration property.

Infinispan checks if lifespan or maximum idle metadata is set and then compares the values with the current time.

If `(creation + lifespan > currentTime)` or `(lastUsed + maxIdle > currentTime)` then Infinispan detects that the entry is expired.

Expiration occurs whenever entries are accessed or found by the expiration reaper.

For example, `k1` reaches the maximum idle time and a client makes a `Cache.get(k1)` request. In this case, Infinispan detects that the entry is expired and removes it from the data container. The `Cache.get()` returns `null`.

Infinispan also expires entries from cache stores, but only with lifespan expiration. Maximum idle expiration does not work with cache stores. In the case of cache loaders, Infinispan cannot expire entries because loaders can only read from external storage.

 Infinispan adds expiration metadata as `long` primitive data types to cache entries. This can increase the size of keys by as much as 32 bytes.

#### 8.3.2. Expiration Reaper

Infinispan uses a reaper thread that runs periodically to detect and remove expired entries. The expiration reaper ensures that expired entries that are no longer accessed are removed.

The Infinispan `ExpirationManager` interface handles the expiration reaper and exposes the `processExpiration()` method.

In some cases, you can disable the expiration reaper and manually expire entries by calling `processExpiration()`; for instance, if you are using local cache mode with a custom application where a maintenance thread runs periodically.

 If you use clustered cache modes, you should never disable the expiration reaper. Infinispan always uses the expiration reaper when using cache stores. In this case you cannot disable it.

#### 8.3.3. Maximum Idle and Clustered Caches

Because maximum idle expiration relies on the last access time for cache entries, it has some limitations with clustered cache modes.

With lifespan expiration, the creation time for cache entries provides a value that is consistent across clustered caches. For example, the creation time for `k1` is always the same on all nodes.

For maximum idle expiration with clustered caches, last access time for entries is not always the same on all nodes. To ensure that entries have the same relative access times across clusters, Infinispan sends touch commands to all owners when keys are accessed.

The touch commands that Infinispan send have the following considerations:

• `Cache.get()` requests do not return until all touch commands complete. This synchronous behavior increases latency of client requests.

• The touch command also updates the "recently accessed" metadata for cache entries on all owners, which Infinispan uses for eviction.

• With scattered cache mode, Infinispan sends touch commands to all nodes, not just primary and backup owners.

• Maximum idle expiration does not work with invalidation mode.

• Iteration across a clustered cache can return expired entries that have exceeded the maximum idle time limit. This behavior ensures performance because no remote invocations are performed during the iteration. Also note that iteration does not refresh any expired entries.

#### 8.3.4. Expiration Examples

When you configure Infinispan to expire entries, you can set lifespan and maximum idle times for:

• All entries in a cache (cache-wide). You can configure cache-wide expiration in `infinispan.xml` or programmatically using the `ConfigurationBuilder`.

• Per entry, which takes priority over cache-wide expiration values. You configure expiration for specific entries when you create them.

 When you explicitly define lifespan and maximum idle time values for cache entries, Infinispan replicates those values across the cluster along with the cache entries. Likewise, Infinispan persists expiration values along with the entries if you configure cache stores.
Configuring expiration for all cache entries

Expire all cache entries after 2 seconds:

``<expiration lifespan="2000" />``

Expire all cache entries 1 second after last access time:

``<expiration max-idle="1000" />``

Disable the expiration reaper with the `interval` attribute and manually expire entries 1 second after last access time:

``<expiration max-idle="1000" interval="-1" />``

Expire all cache entries after 5 seconds or 1 second after the last access time, whichever happens first:

``<expiration lifespan="5000" max-idle="1000" />``
Configuring expiration when creating cache entries

The following example shows how to configure lifespan and maximum idle values when creating cache entries:

``````// Use the cache-wide expiration configuration.
cache.put("pinot noir", pinotNoirPrice); (1)

// Define a lifespan value of 2.
cache.put("chardonnay", chardonnayPrice, 2, TimeUnit.SECONDS); (2)

// Define a lifespan value of -1 (disabled) and a max-idle value of 1.
cache.put("pinot grigio", pinotGrigioPrice,
-1, TimeUnit.SECONDS, 1, TimeUnit.SECONDS); (3)

// Define a lifespan value of 5 and a max-idle value of 1.
cache.put("riesling", rieslingPrice,
5, TimeUnit.SECONDS, 1, TimeUnit.SECONDS); (4)``````

If the Infinispan configuration defines a lifespan value of `1000` for all entries, the preceding `Cache.put()` requests cause the entries to expire:

 1 After 1 second. 2 After 2 seconds. 3 1 second after last access time. 4 After 5 seconds or 1 second after the last access time, whichever happens first.

## 9. Setting Up Persistent Storage

Infinispan can persist in-memory data to external storage, giving you additional capabilities to manage your data such as:

Durability

Adding cache stores allows you to persist data to non-volatile storage so it survives restarts.

Write-through caching

Configuring Infinispan as a caching layer in front of persistent storage simplifies data access for applications because Infinispan handles all interactions with the external storage.

Data overflow

Using eviction and passivation techniques ensures that Infinispan keeps only frequently used data in-memory and writes older entries to persistent storage.

### 9.1. Infinispan Cache Stores

Cache stores connect Infinispan to persistent data sources and implement the following interfaces:

`org.infinispan.persistence.spi.CacheLoader`

Allows Infinispan to load data from persistent storage.

`org.infinispan.persistence.spi.CacheWriter`

Allows Infinispan to persist data to persistent storage.

#### 9.1.1. Configuring Cache Stores

Add cache stores to Infinispan caches in a chain either declaratively or programmatically. Cache read operations check each cache store in the configured order until they locate a valid non-null element of data. Write operations affect all cache stores except for those that you configure as read only.

Procedure
1. Use the `persistence` parameter to configure the persistence layer for caches.

2. Add Infinispan cache stores with the appropriate configuration, as in the following examples:

Declarative configuration for a file-based cache store
``````<persistence passivation="false">
<!-- note that class is missing and is induced by the fileStore element name -->
<file-store
fetch-state="true"
purge="false"
path="${java.io.tmpdir}"> <write-behind thread-pool-size="5" /> </file-store> </persistence>`````` Declarative configuration for a custom cache store configuration ``````<local-cache name="myCustomStore"> <persistence passivation="false"> <store class="org.acme.CustomStore" fetch-state="false" preload="true" shared="false" purge="true" read-only="false" segmented="true"> <write-behind modification-queue-size="123" thread-pool-size="23" /> <property name="myProp">${system.property}</property>
</store>
</persistence>
</local-cache>``````
 Custom cache stores include `property` parameters that let you configure specific attributes for your cache store.
Programmatic configuration for a single file cache store
``````ConfigurationBuilder builder = new ConfigurationBuilder();
builder.persistence()
.passivation(false)
.shared(false)
.fetchPersistentState(true)
.ignoreModifications(false)
.purgeOnStartup(false)
.location(System.getProperty("java.io.tmpdir"))
.async()
.enabled(true)

#### 9.1.2. Setting a Global Persistent Location for File-Based Cache Stores

Infinispan uses a global filesystem location for saving data to persistent storage.

 The global persistent location must be unique to each Infinispan instance. To share data between multiple instances, use a shared persistent location.

Infinispan servers use the `$ISPN_HOME/server/data` directory as the global persistent location. If you are using Infinispan as a library embedded in custom applications, the global persistent location defaults to the `user.dir` system property. This system property typically uses the directory where your application starts. You should configure a global persistent location to use a suitable location. Declarative configuration ``````<cache-container default-cache="myCache"> <global-state> <persistent-location path="example" relative-to="my.data"/> </global-state> ... </cache-container>`````` ``````public GlobalStateConfigurationBuilder persistentLocation(String path, String relativeTo) { persistentLocation.location(example, my.data); return this; }`````` File-Based Cache Stores and Global Persistent Location When using file-based cache stores, you can optionally specify filesystem directories for storage. Unless absolute paths are declared, directories are always relative to the global persistent location. For example, you configure your global persistent location as follows: ``````<global-state> <persistent-location path="/tmp/example" relative-to="my.data"/> </global-state>`````` You then configure a Single File cache store that uses a path named `myDataStore` as follows: ``<file-store path="myDataStore"/>`` In this case, the configuration results in a Single File cache store in `/tmp/example/myDataStore/myCache.dat` If you attempt to set an absolute path that resides outside the global persistent location, Infinispan throws the following exception: `ISPN000558: "The store location 'foo' is not a child of the global persistent location 'bar'"` #### 9.1.3. Passivation Passivation configures Infinispan to write entries to cache stores when it evicts those entries from memory. In this way, passivation ensures that only a single copy of an entry is maintained, either in-memory or in a cache store, which prevents unnecessary and potentially expensive writes to persistent storage. Activation is the process of restoring entries to memory from the cache store when threads attempt to access passivated entries. For this reason, when you enable passivation, you must configure cache stores that implement both `CacheWriter` and `CacheLoader` interfaces so they can write and load entries from persistent storage. When Infinispan evicts an entry from the cache, it notifies cache listeners that the entry is passivated then stores the entry in the cache store. When Infinispan gets an access request for an evicted entry, it lazily loads the entry from the cache store into memory and then notifies cache listeners that the entry is activated.  Passivation uses the first cache loader in the Infinispan configuration and ignores all others. Passivation is not supported with: Transactional stores. Passivation writes and removes entries from the store outside the scope of the actual Infinispan commit boundaries. Shared stores. Shared cache stores require entries to always exist in the store for other owners. For this reason, passivation is not supported because entries cannot be removed. If you enable passivation with transactional stores or shared stores, Infinispan throws an exception. ##### Passivation and Cache Stores Passivation disabled Writes to data in memory result in writes to persistent storage. If Infinispan evicts data from memory, then data in persistent storage includes entries that are evicted from memory. In this way persistent storage is a superset of the in-memory cache. If you do not configure eviction, then data in persistent storage provides a copy of data in memory. Passivation enabled Infinispan adds data to persistent storage only when it evicts data from memory. When Infinispan activates entries, it restores data in memory and deletes data from persistent storage. In this way, data in memory and data in persistent storage form separate subsets of the entire data set, with no intersection between the two.  Entries in persistent storage can become stale when using shared cache stores. This occurs because Infinispan does not delete passivated entries from shared cache stores when they are activated. Values are updated in memory but previously passivated entries remain in persistent storage with out of date values. The following table shows data in memory and in persistent storage after a series of operations: Operation Passivation disabled Passivation enabled Passivation enabled with shared cache store Insert k1. Memory: k1 Disk: k1 Memory: k1 Disk: - Memory: k1 Disk: - Insert k2. Memory: k1, k2 Disk: k1, k2 Memory: k1, k2 Disk: - Memory: k1, k2 Disk: - Eviction thread runs and evicts k1. Memory: k2 Disk: k1, k2 Memory: k2 Disk: k1 Memory: k2 Disk: k1 Read k1. Memory: k1, k2 Disk: k1, k2 Memory: k1, k2 Disk: - Memory: k1, k2 Disk: k1 Eviction thread runs and evicts k2. Memory: k1 Disk: k1, k2 Memory: k1 Disk: k2 Memory: k1 Disk: k1, k2 Remove k2. Memory: k1 Disk: k1 Memory: k1 Disk: - Memory: k1 Disk: k1 #### 9.1.4. Cache Loaders and Transactional Caches Only JDBC String-Based cache stores support transactional operations. If you configure caches as transactional, you should set `transactional=true` to keep data in persistent storage synchronized with data in memory. For all other cache stores, Infinispan does not enlist cache loaders in transactional operations. This can result in data inconsistency if transactions succeed in modifying data in memory but do not completely apply changes to data in the cache store. In this case manual recovery does not work with cache stores. Reference #### 9.1.5. Segmented Cache Stores Cache stores can organize data into hash space segments to which keys map. Segmented stores increase read performance for bulk operations; for example, streaming over data (`Cache.size`, `Cache.entrySet.stream`), pre-loading the cache, and doing state transfer operations. However, segmented stores can also result in loss of performance for write operations. This performance loss applies particularly to batch write operations that can take place with transactions or write-behind stores. For this reason, you should evaluate the overhead for write operations before you enable segmented stores. The performance gain for bulk read operations might not be acceptable if there is a significant performance loss for write operations.  The number of segments you configure for cache stores must match the number of segments you define in the Infinispan configuration with the `clustering.hash.numSegments` parameter. If you change the `numSegments` parameter in the configuration after you add a segmented cache store, Infinispan cannot read data from that cache store. Reference Key Ownership #### 9.1.6. Filesystem-Based Cache Stores In most cases, filesystem-based cache stores are appropriate for local cache stores for data that overflows from memory because it exceeds size and/or time restrictions.  You should not use filesystem-based cache stores on shared file systems such as an NFS, Microsoft Windows, or Samba share. Shared file systems do not provide file locking capabilities, which can lead to data corruption. Likewise, shared file systems are not transactional. If you attempt to use transactional caches with shared file systems, unrecoverable failures can happen when writing to files during the commit phase. #### 9.1.7. Write-Through Write-Through is an cache writing mode where writes to memory and writes to cache stores are synchronous. When a client application updates a cache entry, in most cases by invoking `Cache.put()`, Infinispan does not return the call until it updates the cache store. This cache writing mode results in updates to the cache store concluding within the boundaries of the client thread. The primary advantage of Write-Through mode is that the cache and cache store are updated simultaneously, which ensures that the cache store is always consistent with the cache. However, Write-Through mode can potentially decrease performance because the need to access and update cache stores directly adds latency to cache operations. Infinispan defaults to Write-Through mode unless you explicitly configure Write-Behind mode on cache stores. Write-through configuration ``````<persistence passivation="false"> <file-store fetch-state="true" read-only="false" purge="false" path="${java.io.tmpdir}"/>
</persistence>``````
Reference

Write-Behind

#### 9.1.8. Write-Behind

Write-Behind is an cache writing mode where writes to memory are synchronous and writes to cache stores are asynchronous. When a client application updates a cache entry, Infinispan adds the update to a modification queue and then modifies the cache store in a different thread than the client thread.

You can configure the number of threads that consume the modification queue and apply updates to the underlying cache store. The modification queue fills up if there are not enough threads to handle the updates or if the underlying cache store becomes unavailable. When this occurs, Infinispan uses Write-Through mode until the modification queue can accept new entries.

Write-Behind mode provides a performance advantage over Write-Through mode because cache operations do not need to wait for updates to the underlying cache store to complete. However, data in the cache store remains inconsistent with data in the cache until the modification queue is processed. For this reason, Write-Behind mode is suitable for cache stores with low latency, such as unshared and local filesystem-based cache stores, where the time between the write to the cache and the write to the cache store is as small as possible.

Write-behind configuration
``````<persistence passivation="false">
<file-store fetch-state="true"
purge="false" path="\${java.io.tmpdir}">
<write-behind modification-queue-size="123"
fail-silently="true"/>
</file-store>
</persistence>``````

The preceding configuration example uses the `fail-silently` parameter to control what happens when either the cache store is unavailable or the modification queue is full.

• If `fail-silently="true"` then Infinispan logs WARN messages and rejects write operations.

• If `fail-silently="false"` then Infinispan throws exceptions if it detects the cache store is unavailable during a write operation. Likewise if the modification queue becomes full, Infinispan throws an exception.

In some cases, data loss can occur if Infinispan restarts and write operations exist in the modification queue. For example the cache store goes offline but, during the time it takes to detect that the cache store is unavailable, write operations are added to the modification queue because it is not full. If Infinispan restarts or otherwise becomes unavailable before the cache store comes back online, then the write operations in the modification queue are lost because they were not persisted.

Reference

Write-Through

### 9.2. Cache Store Implementations

Infinispan provides several cache store implementations that you can use. Alternatively you can provide custom cache stores.

`ClusterCacheLoader` retrieves data from other Infinispan cluster members but does not persist data. In other words, `ClusterCacheLoader` is not a cache store.

`ClusterCacheLoader` provides a non-blocking partial alternative to state transfer. `ClusterCacheLoader` fetches keys from other nodes on demand if those keys are not available on the local node, which is similar to lazily loading cache content.

The following points also apply to `ClusterCacheLoader`:

• Preloading does not take effect (`preload=true`).

• Fetching persistent state is not supported (`fetch-state=true`).

• Segmentation is not supported.

Declarative configuration
``````<persistence>
</persistence>``````
Programmatic configuration
``````ConfigurationBuilder b = new ConfigurationBuilder();
b.persistence()
.remoteCallTimeout(500);``````

#### 9.2.2. Single File Cache Stores

Single File cache stores, `SingleFileStore`, persist data to file. Infinispan also maintains an in-memory index of keys while keys and values are stored in the file. By default, Single File cache stores are segmented, which means that Infinispan creates a separate file for each segment.

Because `SingleFileStore` keeps an in-memory index of keys and the location of values, it requires additional memory, depending on the key size and the number of keys. For this reason, `SingleFileStore` is not recommended for use cases where the keys have a large size.

In some cases, `SingleFileStore` can also become fragmented. If the size of values continually increases, available space in the single file is not used but the entry is appended to the end of the file. Available space in the file is used only if an entry can fit within it. Likewise, if you remove all entries from memory, the single file store does not decrease in size or become defragmented.

Declarative configuration
``````<persistence>
<file-store max-entries="5000"/>
</persistence>``````
Programmatic configuration
• For embedded deployments, do the following:

``````ConfigurationBuilder b = new ConfigurationBuilder();
b.persistence()
.maxEntries(5000);``````
• For server deployments, do the following:

``````import org.infinispan.client.hotrod.configuration.ConfigurationBuilder;
import org.infinispan.client.hotrod.configuration.NearCacheMode;
...

ConfigurationBuilder builder = new ConfigurationBuilder();
builder
.remoteCache("mycache")
.configuration("<infinispan><cache-container><distributed-cache name=\"mycache\"><persistence><file-store max-entries=\"5000\"/></persistence></distributed-cache></cache-container></infinispan>");``````
Segmentation

Single File cache stores support segmentation and create a separate instance per segment, which results in multiple directories in the path you configure. Each directory is a number that represents the segment to which the data maps.

#### 9.2.3. JDBC String-Based Cache Stores

JDBC String-Based cache stores, `JdbcStringBasedStore`, use JDBC drivers to load and store values in the underlying database.

`JdbcStringBasedStore` stores each entry in its own row in the table to increase throughput for concurrent loads. `JdbcStringBasedStore` also uses a simple one-to-one mapping that maps each key to a `String` object using the `key-to-string-mapper` interface.

Infinispan provides a default implementation, `DefaultTwoWayKey2StringMapper`, that handles primitive types.

 By default Infinispan shares are not stored, which means that all nodes in the cluster write to the underlying store on each update. If you want operations to write to the underlying database once only, you must configure JDBC store as shared.
Segmentation

`JdbcStringBasedStore` uses segmentation by default and requires a column in the database table to represent the segments to which entries belong.

##### Connection Factories

`JdbcStringBasedStore` relies on a `ConnectionFactory` implementation to connection to a database.

Infinispan provides the following `ConnectionFactory` implementations:

`PooledConnectionFactoryConfigurationBuilder`

A connection factory based on Agroal that you configure via `PooledConnectionFactoryConfiguration`.

Alternatively, you can specify configuration properties prefixed with `org.infinispan.agroal.` as in the following example:

``````org.infinispan.agroal.metricsEnabled=false

org.infinispan.agroal.minSize=10
org.infinispan.agroal.maxSize=100
org.infinispan.agroal.initialSize=20
org.infinispan.agroal.acquisitionTimeout_s=1
org.infinispan.agroal.validationTimeout_m=1
org.infinispan.agroal.leakTimeout_s=10
org.infinispan.agroal.reapTimeout_m=10

org.infinispan.agroal.metricsEnabled=false
org.infinispan.agroal.autoCommit=true
org.infinispan.agroal.jdbcUrl=jdbc:h2:mem:PooledConnectionFactoryTest;DB_CLOSE_DELAY=-1
org.infinispan.agroal.driverClassName=org.h2.Driver.class
org.infinispan.agroal.principal=sa
org.infinispan.agroal.credential=sa``````

You then configure Infinispan to use your properties file via `PooledConnectionFactoryConfiguration.propertyFile`.

 You should use `PooledConnectionFactory` with standalone deployments, rather than deployments in servlet containers.
`ManagedConnectionFactoryConfigurationBuilder`

A connection factory that you can can use with managed environments such as application servers. This connection factory can explore a configurable location in the JNDI tree and delegate connection management to the `DataSource`.

`SimpleConnectionFactoryConfigurationBuilder`

A connection factory that creates database connections on a per invocation basis. You should use this connection factory for test or development environments only.

##### JDBC String-Based Cache Store Configuration

You can configure `JdbcStringBasedStore` programmatically or declaratively.

Declarative configuration
• Using `PooledConnectionFactory`

``````<persistence>
<string-keyed-jdbc-store xmlns="urn:infinispan:config:store:jdbc:10.1" shared="true">
<connection-pool connection-url="jdbc:h2:mem:infinispan_string_based;DB_CLOSE_DELAY=-1"
driver="org.h2.Driver"/>
<string-keyed-table drop-on-exit="true"
prefix="ISPN_STRING_TABLE">
<id-column name="ID_COLUMN" type="VARCHAR(255)" />
<data-column name="DATA_COLUMN" type="BINARY" />
<timestamp-column name="TIMESTAMP_COLUMN" type="BIGINT" />
<segment-column name="SEGMENT_COLUMN" type="INT" />
</string-keyed-table>
</string-keyed-jdbc-store>
</persistence>``````
• Using `ManagedConnectionFactory`

``````<persistence>
<string-keyed-jdbc-store xmlns="urn:infinispan:config:store:jdbc:10.1" shared="true">
<data-source jndi-url="java:/StringStoreWithManagedConnectionTest/DS" />
<string-keyed-table drop-on-exit="true"
create-on-start="true"
prefix="ISPN_STRING_TABLE">
<id-column name="ID_COLUMN" type="VARCHAR(255)" />
<data-column name="DATA_COLUMN" type="BINARY" />
<timestamp-column name="TIMESTAMP_COLUMN" type="BIGINT" />
<segment-column name="SEGMENT_COLUMN" type="INT"/>
</string-keyed-table>
</string-keyed-jdbc-store>
</persistence>``````
Programmatic configuration
• Using `PooledConnectionFactory`

``````ConfigurationBuilder builder = new ConfigurationBuilder();
.fetchPersistentState(false)
.ignoreModifications(false)
.purgeOnStartup(false)
.shared(true)
.table()
.dropOnExit(true)
.createOnStart(true)
.tableNamePrefix("ISPN_STRING_TABLE")
.idColumnName("ID_COLUMN").idColumnType("VARCHAR(255)")
.dataColumnName("DATA_COLUMN").dataColumnType("BINARY")
.timestampColumnName("TIMESTAMP_COLUMN").timestampColumnType("BIGINT")
.segmentColumnName("SEGMENT_COLUMN").segmentColumnType("INT")
.connectionPool()
.connectionUrl("jdbc:h2:mem:infinispan_string_based;DB_CLOSE_DELAY=-1")
.driverClass("org.h2.Driver");``````
• Using `ManagedConnectionFactory`

``````ConfigurationBuilder builder = new ConfigurationBuilder();
.fetchPersistentState(false)
.ignoreModifications(false)
.purgeOnStartup(false)
.shared(true)
.table()
.dropOnExit(true)
.createOnStart(true)
.tableNamePrefix("ISPN_STRING_TABLE")
.idColumnName("ID_COLUMN").idColumnType("VARCHAR(255)")
.dataColumnName("DATA_COLUMN").dataColumnType("BINARY")
.timestampColumnName("TIMESTAMP_COLUMN").timestampColumnType("BIGINT")
.segmentColumnName("SEGMENT_COLUMN").segmentColumnType("INT")
.dataSource()
.jndiUrl("java:/StringStoreWithManagedConnectionTest/DS");``````

#### 9.2.4. JPA Cache Stores

JPA (Java Persistence API) cache stores, `JpaStore`, use formal schema to persist data. Other applications can then read from persistent storage to load data from Infinispan. However, other applications should not use persistent storage concurrently with Infinispan.

When using `JpaStore`, you should take the following into consideration:

• Keys should be the ID of the entity. Values should be the entity object.

• Only a single `@Id` or `@EmbeddedId` annotation is allowed.

• Auto-generated IDs with the `@GeneratedValue` annotation are not supported.

• All entries are stored as immortal.

• `JpaStore` does not support segmentation.

Declarative configuration
``````<local-cache name="vehicleCache">
<persistence passivation="false">
<jpa-store xmlns="urn:infinispan:config:store:jpa:10.1"
persistence-unit="org.infinispan.persistence.jpa.configurationTest"
entity-class="org.infinispan.persistence.jpa.entity.Vehicle">
/>
</persistence>
</local-cache>``````
Parameter Description

`persistence-unit`

Specifies the JPA persistence unit name in the JPA configuration file, `persistence.xml`, that contains the JPA entity class.

`entity-class`

Specifies the fully qualified JPA entity class name that is expected to be stored in this cache. Only one class is allowed.

Programmatic configuration
``````Configuration cacheConfig = new ConfigurationBuilder().persistence()
.entityClass(User.class)
.build();``````
Parameter Description

`persistenceUnitName`

Specifies the JPA persistence unit name in the JPA configuration file, `persistence.xml`, that contains the JPA entity class.

`entityClass`

Specifies the fully qualified JPA entity class name that is expected to be stored in this cache. Only one class is allowed.

##### JPA Cache Store Usage Example

This section provides an example for using JPA cache stores.

Prerequistes
• Configure Infinispan to marshall your JPA entities. By default, Infinispan uses ProtoStream for marshalling Java objects. To marshall JPA entities, you must create a `SerializationContextInitializer` implementation that registers a `.proto` schema and marshaller with a `SerializationContext`.

Procedure
1. Define a persistence unit "myPersistenceUnit" in `persistence.xml`.

``````<persistence-unit name="myPersistenceUnit">
...
</persistence-unit>``````
2. Create a user entity class.

``````@Entity
public class User implements Serializable {
@Id
private String firstName;
private String lastName;

...
}``````
3. Configure a cache named "usersCache" with a JPA cache store.

Then you can configure a cache "usersCache" to use JPA Cache Store, so that when you put data into the cache, the data would be persisted into the database based on JPA configuration.

``````EmbeddedCacheManager cacheManager = ...;

Configuration cacheConfig = new ConfigurationBuilder().persistence()
.entityClass(User.class)
.build();
cacheManager.defineCache("usersCache", cacheConfig);

Cache<String, User> usersCache = cacheManager.getCache("usersCache");
usersCache.put("raytsang", new User(...));``````
• Caches that use a JPA cache store can store one type of data only, as in the following example:

``````Cache<String, User> usersCache = cacheManager.getCache("myJPACache");
// Cache is configured for the User entity class
// Cannot configure caches to use another entity class with JPA cache stores
Cache<Integer, Teacher> teachersCache = cacheManager.getCache("myJPACache");
teachersCache.put(1, new Teacher());
// The put request does not work for the Teacher entity class``````
• The `@EmbeddedId` annotation allows you to use composite keys, as in the following example:

``````@Entity
public class Vehicle implements Serializable {
@EmbeddedId
private VehicleId id;
private String color;        ...
}

@Embeddable
public class VehicleId implements Serializable
{
private String state;
...
}``````

#### 9.2.5. Remote Cache Stores

Remote cache stores, `RemoteStore`, use a remote Infinispan cluster as storage.

`RemoteStore` uses the Hot Rod protocol to communicate with remote Infinispan clusters.

In the following configuration examples, `RemoteStore` uses the remote cache named "mycache" on Infinispan servers "one" and "two":

Declarative configuration
``````<persistence>
<remote-store xmlns="urn:infinispan:config:store:remote:10.1" cache="mycache" raw-values="true">
<remote-server host="one" port="12111" />
<remote-server host="two" />
<connection-pool max-active="10" exhausted-action="CREATE_NEW" />
<write-behind />
</remote-store>
</persistence>``````
Programmatic configuration
``````ConfigurationBuilder b = new ConfigurationBuilder();
.fetchPersistentState(false)
.ignoreModifications(false)
.purgeOnStartup(false)
.remoteCacheName("mycache")
.rawValues(true)
.host("one").port(12111)
.host("two")
.connectionPool()
.maxActive(10)
.exhaustedAction(ExhaustedAction.CREATE_NEW)
.async().enable();``````
Segmentation

`RemoteStore` supports segmentation and can publish keys and entries by segment, which makes bulk operations more efficient. However, segmentation is available with Infinispan Hot Rod protocol version 2.3 or later.

 Ensure the number of segments and hash are the same between the Remote cache store and Infinispan servers, otherwise bulk operations do not return correct results.

#### 9.2.6. RocksDB Cache Stores

RocksDB provides key-value filesystem-based storage with high performance and reliability for highly concurrent environments.

RocksDB cache stores, `RocksDBStore`, use two databases. One database provides a primary cache store for data in memory; the other database holds entries that Infinispan expires from memory.

Declarative configuration
``````<local-cache name="vehicleCache">
<persistence>
<rocksdb-store xmlns="urn:infinispan:config:store:rocksdb:10.1" path="rocksdb/data">
<expiration path="rocksdb/expired"/>
</rocksdb-store>
</persistence>
</local-cache>``````
Programmatic configuration
``````Configuration cacheConfig = new ConfigurationBuilder().persistence()
.build();
EmbeddedCacheManager cacheManager = new DefaultCacheManager(cacheConfig);

Cache<String, User> usersCache = cacheManager.getCache("usersCache");
usersCache.put("raytsang", new User(...));``````
``````Properties props = new Properties();
props.put("database.max_background_compactions", "2");
props.put("data.write_buffer_size", "512MB");

Configuration cacheConfig = new ConfigurationBuilder().persistence()
.location("rocksdb/data")
.expiredLocation("rocksdb/expired")
.properties(props)
.build();``````
Table 1. `RocksDBStore` configuration parameters
Parameter Description

`location`

Specifies the path to the RocksDB database that provides the primary cache store. If you do not set the location, it is automatically created. Note that the path must be relative to the global persistent location.

`expiredLocation`

Specifies the path to the RocksDB database that provides the cache store for expired data. If you do not set the location, it is automatically created. Note that the path must be relative to the global persistent location.

`expiryQueueSize`

Sets the size of the in-memory queue for expiring entries. When the queue reaches the size, Infinispan flushes the expired into the RocksDB cache store.

`clearThreshold`

Sets the maximum number of entries before deleting and re-initializing (re-init) the RocksDB database. For smaller size cache stores, iterating through all entries and removing each one individually can provide a faster method.

RocksDB tuning parameters

You can also specify the following RocksDB tuning parameters:

• `compressionType`

• `blockSize`

• `cacheSize`

RocksDB configuration properties

Optionally set properties in the configuration as follows:

• Prefix properties with `database` to adjust and tune RocksDB databases.

• Prefix properties with `data` to configure the column families in which RocksDB stores your data.

```<property name="database.max_background_compactions">2</property>
<property name="data.write_buffer_size">64MB</property>```
Segmentation

`RocksDBStore` supports segmentation and creates a separate column family per segment. Segmented RocksDB cache stores improve lookup performance and iteration but slightly lower performance of write operations.

 You should not configure more than a few hundred segments. RocksDB is not designed to have an unlimited number of column families. Too many segments also significantly increases cache store start time.

#### 9.2.7. Soft-Index File Stores

Soft-Index File cache stores, `SoftIndexFileStore`, provide local file-based storage.

`SoftIndexFileStore` is a Java implementation that uses a variant of B+ Tree that is cached in-memory using Java soft references. The B+ Tree, called `Index` is offloaded on the file system to a single file that is purged and rebuilt each time the cache store restarts.

`SoftIndexFileStore` stores data in a set of files rather than a single file. When usage of any file drops below 50%, the entries in the file are overwritten to another file and the file is then deleted.

`SoftIndexFileStore` persists data in a set of files that are written in an append-only method. For this reason, if you use `SoftIndexFileStore` on conventional magnetic disk, it does not need to seek when writing a burst of entries.

Most structures in `SoftIndexFileStore` are bounded, so out-of-memory exceptions do not pose a risk. You can also configure limits for concurrently open files.

By default the size of a node in the `Index` is limited to 4096 bytes. This size also limits the key length; more precisely the length of serialized keys. For this reason, you cannot use keys longer than the size of the node, 15 bytes. Additionally, key length is stored as "short", which limits key length to 32767 bytes. `SoftIndexFileStore` throws an exception if keys are longer after serialization occurs.

`SoftIndexFileStore` cannot detect expired entries, which can lead to excessive usage of space on the file system .

 `AdvancedStore.purgeExpired()` is not implemented in `SoftIndexFileStore`.
Declarative configuration
``````<persistence>
<soft-index-file-store xmlns="urn:infinispan:config:store:soft-index:10.1">
<index path="testCache/index" />
<data path="testCache/data" />
</soft-index-file-store>
</persistence>``````
Programmatic configuration
``````ConfigurationBuilder b = new ConfigurationBuilder();
b.persistence()
.indexLocation("testCache/index");
.dataLocation("testCache/data")``````
Segmentation

Soft-Index File cache stores support segmentation and create a separate instance per segment, which results in multiple directories in the path you configure. Each directory is a number that represents the segment to which the data maps.

#### 9.2.8. Custom Cache Stores

You can create custom cache stores that implement one or more of the Infinispan persistent SPIs.

Reference
##### Implementing Custom Cache Stores

Create custom cache stores that implement both `CacheWriter` and `CacheLoader` interfaces to fetch and persist data to external storage.

1. Implement the appropriate Infinispan persistent SPIs.

2. Annotate your store class with the `@Store` annotation and specify the appropriate properties.

For example, if your cache store is shared, use the `@Store(shared = true)` annotation.

3. Create a custom cache store configuration and builder.

1. Extend `AbstractStoreConfiguration` and `AbstractStoreConfigurationBuilder`.

Extend `AbstractSegmentedStoreConfiguration` instead of `AbstractStoreConfiguration` for a segmented cache store that creates a different store instance per segment.

2. Optionally add the following annotations to ensure that your custom configuration builder parses your cache store configuration from XML:

• `@ConfigurationFor`

• `@BuiltBy`

• `@ConfiguredBy`

If you do not add these annotations, then `CustomStoreConfigurationBuilder` parses the common store attributes defined in `AbstractStoreConfiguration` and any additional elements are ignored.

 If a store and its configuration do not declare the `@Store` and `@ConfigurationFor` annotations, a warning message is logged when Infinispan initializes the cache.
##### Custom Cache Store Configuration

After you implement your custom cache store, configure Infinispan to use it.

Declarative configuration
``````<local-cache name="customStoreExample">
<persistence>
<store class="org.infinispan.persistence.dummy.DummyInMemoryStore" />
</persistence>
</local-cache>``````
Programmatic configuration
``````Configuration config = new ConfigurationBuilder()
.persistence()
.build();``````
##### Deploying Custom Cache Stores

You can package custom cache stores into JAR files and deploy them to Infinispan servers as follows:

1. Package your custom cache store implementation in a JAR file.

2. Add a file under `META-INF/services/` that contains the fully qualified class name of your store implementation.

The name of the service file should reflect the interface that your store implements. For example, if your store implements the `AdvancedCacheWriter` interface then you should create the following file:

`/META-INF/services/org.infinispan.persistence.spi.AdvancedCacheWriter`

3. Add your JAR file to the `server/lib` directory of your Infinispan server.

### 9.3. Infinispan Persistence SPIs

Infinispan Service Provider Interfaces (SPI) enable read and write operations to external storage and provide the following features:

Portability across JCache-compliant vendors

The Infinispan `CacheWriter` and `CacheLoader` interfaces align with the `JSR-107` JCache specification.

Simplified transaction integration

Infinispan automatically handles locking so your implementations do not need to coordinate concurrent access to persistent stores. Depending on the locking mode you use, concurrent writes to the same key generally do not occur. However, you should expect operations on the persistent storage to originate from multiple threads and create implementations to tolerate this behavior.

Parallel iteration

Infinispan lets you iterate over entries in persistent stores with multiple threads in parallel.

Reduced serialization resulting in less CPU usage

Infinispan exposes stored entries in a serialized format that can be transmitted remotely. For this reason, Infinispan does not need to deserialize entries that it retrieves from persistent storage and then serialize again when writing to the wire.

Reference

#### 9.3.1. Persistence SPI Classes

The following notes apply to Infinispan persistence SPI classes:

ByteBuffer

Abstracts the serialized form of an object.

MarshallableEntry

Abstracts the information held within a persistent store corresponding to a key/value added to the cache. Provides a method for reading this information both in serialized (ByteBuffer) and deserialized (Object) format. Normally data read from the store is kept in serialized format and lazily deserialized on demand, within the MarshallableEntry implementation.

Provide basic methods for writing to and reading from cache stores.

Provide bulk operations to manipulate the underlaying storage, such as parallel iteration and purging of expired entries, clear and size.

Provides all the operations that deal with segments.

Cache stores can be segmented if they do one of the following:

• Implement the SegmentedAdvancedLoadWriteStore interface. In this case only a single store instance is used per cache.

• Has a configuration that extends the AbstractSegmentedConfiguration abstract class.

This requires you to implement the `newConfigurationFrom()` method where it is expected that a new `StoreConfiguration` instance is created per invocation. This creates a store instance per segment to which a node can write. Stores might start and stop as data is moved between nodes.

A provider might choose to only implement a subset of these interfaces:

• Not implementing the AdvancedCacheWriter makes the given writer not usable for purging expired entries or clear

If you want to migrate your existing store to the new API or to write a new cache store implementation, the SingleFileStore provides a good starting point.

### 9.4. Migrating Between Cache Stores

Infinispan provides a utility to migrate data from one cache store to another.

#### 9.4.1. Cache Store Migrator

Infinispan provides the `StoreMigrator.java` utility that recreates data for the latest Infinispan cache store implementations.

`StoreMigrator` takes a cache store from a previous version of Infinispan as source and uses a cache store implementation as target.

When you run `StoreMigrator`, it creates the target cache with the cache store type that you define using the `EmbeddedCacheManager` interface. `StoreMigrator` then loads entries from the source store into memory and then puts them into the target cache.

`StoreMigrator` also lets you migrate data from one type of cache store to another. For example, you can migrate from a JDBC String-Based cache store to a Single File cache store.

 `StoreMigrator` cannot migrate data from segmented cache stores to: Non-segmented cache store. Segmented cache stores that have a different number of segments.

#### 9.4.2. Getting the Store Migrator

`StoreMigrator` is available as part of the Infinispan tools library, `infinispan-tools`, and is included in the Maven repository.

Procedure
• Configure your `pom.xml` for `StoreMigrator` as follows:

``````<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>

<groupId>org.infinispan.example</groupId>
<artifactId>jdbc-migrator-example</artifactId>
<version>1.0-SNAPSHOT</version>

<dependencies>
<dependency>
<groupId>org.infinispan</groupId>
<artifactId>infinispan-tools</artifactId>
</dependency>
</dependencies>

<build>
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>exec-maven-plugin</artifactId>
<version>1.2.1</version>
<executions>
<execution>
<goals>
<goal>java</goal>
</goals>
</execution>
</executions>
<configuration>
<mainClass>org.infinispan.tools.store.migrator.StoreMigrator</mainClass>
<arguments>
<argument>path/to/migrator.properties</argument>
</arguments>
</configuration>
</plugin>
</plugins>
</build>
</project>``````

#### 9.4.3. Configuring the Store Migrator

Set properties for source and target cache stores in a `migrator.properties` file.

Procedure
1. Create a `migrator.properties` file.

2. Configure the source cache store in `migrator.properties`.

1. Prepend all configuration properties with `source.` as in the following example:

```source.type=SOFT_INDEX_FILE_STORE
source.cache_name=myCache
source.location=/path/to/source/sifs```
3. Configure the target cache store in `migrator.properties`.

1. Prepend all configuration properties with `target.` as in the following example:

```target.type=SINGLE_FILE_STORE
target.cache_name=myCache
target.location=/path/to/target/sfs.dat```
##### Store Migrator Properties

Configure source and target cache stores in a `StoreMigrator` properties.

Table 2. Cache Store Type Property
Property Description Required/Optional

`type`

Specifies the type of cache store type for a source or target.

`.type=JDBC_STRING`

`.type=JDBC_BINARY`

`.type=JDBC_MIXED`

`.type=LEVELDB`

`.type=ROCKSDB`

`.type=SINGLE_FILE_STORE`

`.type=SOFT_INDEX_FILE_STORE`

`.type=JDBC_MIXED`

Required

Table 3. Common Properties
Property Description Example Value Required/Optional

`cache_name`

Names the cache that the store backs.

`.cache_name=myCache`

Required

`segment_count`

Specifies the number of segments for target cache stores that can use segmentation.

The number of segments must match `clustering.hash.numSegments` in the Infinispan configuration.

In other words, the number of segments for a cache store must match the number of segments for the corresponding cache. If the number of segments is not the same, Infinispan cannot read data from the cache store.

`.segment_count=256`

Optional

Table 4. JDBC Properties
Property Description Required/Optional

`dialect`

Specifies the dialect of the underlying database.

Required

`version`

Specifies the marshaller version for source cache stores. Set one of the following values:

* `8` for Infinispan 8.x

* `9` for Infinispan 9.x

* `10` Infinispan 10.x

Required for source stores only.

For example: `source.version=9`

`marshaller.class`

Specifies a custom marshaller class.

Required if using custom marshallers.

`marshaller.externalizers`

Specifies a comma-separated list of custom `AdvancedExternalizer` implementations to load in this format: `[id]:<Externalizer class>`

Optional

`connection_pool.connection_url`

Specifies the JDBC connection URL.

Required

`connection_pool.driver_class`

Specifies the class of the JDBC driver.

Required

`connection_pool.username`

Required

`connection_pool.password`

Required

`db.major_version`

Sets the database major version.

Optional

`db.minor_version`

Sets the database minor version.

Optional

`db.disable_upsert`

Disables database upsert.

Optional

`db.disable_indexing`

Specifies if table indexes are created.

Optional

`table.string.table_name_prefix`

Specifies additional prefixes for the table name.

Optional

`table.string.<id|data|timestamp>.name`

Specifies the column name.

Required

`table.string.<id|data|timestamp>.type`

Specifies the column type.

Required

`key_to_string_mapper`

Specifies the `TwoWayKey2StringMapper` class.

Optional

 To migrate from Binary cache stores in older Infinispan versions, change `table.string.*` to `table.binary.\*` in the following properties: `source.table.binary.table_name_prefix` `source.table.binary..name` `source.table.binary..type`
```# Example configuration for migrating to a JDBC String-Based cache store
target.type=STRING
target.cache_name=myCache
target.dialect=POSTGRES
target.marshaller.class=org.example.CustomMarshaller
target.marshaller.externalizers=25:Externalizer1,org.example.Externalizer2
target.connection_pool.connection_url=jdbc:postgresql:postgres
target.connection_pool.driver_class=org.postrgesql.Driver
target.db.major_version=9
target.db.minor_version=5
target.db.disable_upsert=false
target.db.disable_indexing=false
target.table.string.table_name_prefix=tablePrefix
target.table.string.id.name=id_column
target.table.string.data.name=datum_column
target.table.string.timestamp.name=timestamp_column
target.table.string.id.type=VARCHAR
target.table.string.data.type=bytea
target.table.string.timestamp.type=BIGINT
target.key_to_string_mapper=org.infinispan.persistence.keymappers. DefaultTwoWayKey2StringMapper```
Table 5. RocksDB Properties
Property Description Required/Optional

`location`

Sets the database directory.

Required

`compression`

Specifies the compression type to use.

Optional

```# Example configuration for migrating from a RocksDB cache store.
source.type=ROCKSDB
source.cache_name=myCache
source.location=/path/to/rocksdb/database
source.compression=SNAPPY```
Table 6. SingleFileStore Properties
Property Description Required/Optional

`location`

Sets the directory that contains the cache store `.dat` file.

Required

```# Example configuration for migrating to a Single File cache store.
target.type=SINGLE_FILE_STORE
target.cache_name=myCache
target.location=/path/to/sfs.dat```
Table 7. SoftIndexFileStore Properties
Property Description Value

Required/Optional

`location`

Sets the database directory.

Required

`index_location`

Sets the database index directory.

```# Example configuration for migrating to a Soft-Index File cache store.
target.type=SOFT_INDEX_FILE_STORE
target.cache_name=myCache
target.location=path/to/sifs/database
target.location=path/to/sifs/index```

#### 9.4.4. Migrating Cache Stores

Run `StoreMigrator` to migrate data from one cache store to another.

Prerequisites
• Get `infinispan-tools.jar`.

• Create a `migrator.properties` file that configures the source and target cache stores.

Procedure
• If you build `infinispan-tools.jar` from source, do the following:

1. Add `infinispan-tools.jar` and dependencies for your source and target databases, such as JDBC drivers, to your classpath.

2. Specify `migrator.properties` file as an argument for `StoreMigrator`.

• If you pull `infinispan-tools.jar` from the Maven repository, run the following command:

`mvn exec:java`

## 10. Setting Up Partition Handling

### 10.1. Partition handling

An Infinispan cluster is built out of a number of nodes where data is stored. In order not to lose data in the presence of node failures, Infinispan copies the same data — cache entry in Infinispan parlance — over multiple nodes. This level of data redundancy is configured through the `numOwners` configuration attribute and ensures that as long as fewer than `numOwners` nodes crash simultaneously, Infinispan has a copy of the data available.

However, there might be catastrophic situations in which more than `numOwners` nodes disappear from the cluster:

Split brain

Caused e.g. by a router crash, this splits the cluster in two or more partitions, or sub-clusters that operate independently. In these circumstances, multiple clients reading/writing from different partitions see different versions of the same cache entry, which for many application is problematic. Note there are ways to alleviate the possibility for the split brain to happen, such as redundant networks or IP bonding. These only reduce the window of time for the problem to occur, though.

`numOwners` nodes crash in sequence

When at least `numOwners` nodes crash in rapid succession and Infinispan does not have the time to properly rebalance its state between crashes, the result is partial data loss.

The partition handling functionality discussed in this section allows the user to configure what operations can be performed on a cache in the event of a split brain occurring. Infinispan provides multiple partition handling strategies, which in terms of Brewer’s CAP theorem determine whether availability or consistency is sacrificed in the presence of partition(s). Below is a list of the provided strategies:

Strategy Description CAP

If the partition does not have all owners for a given segment, both reads and writes are denied for all keys in that segment.

Consistency

Allows reads for a given key if it exists in this partition, but only allows writes if this partition contains all owners of a segment. This is still a consistent approach because some entries are readable if available in this partition, but from a client application perspective it is not deterministic.

Consistency

Allow entries on each partition to diverge, with conflict resolution attempted upon the partitions merging.

Availability

The requirements of your application should determine which strategy is appropriate. For example, DENY_READ_WRITES is more appropriate for applications that have high consistency requirements; i.e. when the data read from the system must be accurate. Whereas if Infinispan is used as a best-effort cache, partitions maybe perfectly tolerable and the ALLOW_READ_WRITES might be more appropriate as it favours availability over consistency.

The following sections describe how Infinispan handles split brain and successive failures for each of the partition handling strategies. This is followed by a section describing how Infinispan allows for automatic conflict resolution upon partition merges via merge policies. Finally, we provide a section describing how to configure partition handling strategies and merge policies.

#### 10.1.1. Split brain

In a split brain situation, each network partition will install its own JGroups view, removing the nodes from the other partition(s). We don’t have a direct way of determining whether the has been split into two or more partitions, since the partitions are unaware of each other. Instead, we assume the cluster has split when one or more nodes disappear from the JGroups cluster without sending an explicit leave message.

##### Split Strategies

In this section, we detail how each partition handling strategy behaves in the event of split brain occurring.

Each partition continues to function as an independent cluster, with all partitions remaining in AVAILABLE mode. This means that each partition may only see a part of the data, and each partition could write conflicting updates in the cache. During a partition merge these conflicts are automatically resolved by utilising the ConflictManager and the configured EntryMergePolicy.

When a split is detected each partition does not start a rebalance immediately, but first it checks whether it should enter DEGRADED mode instead:

• If at least one segment has lost all its owners (meaning at least numOwners nodes left since the last rebalance ended), the partition enters DEGRADED mode.

• If the partition does not contain a simple majority of the nodes (floor(numNodes/2) + 1) in the latest stable topology, the partition also enters DEGRADED mode.

• Otherwise the partition keeps functioning normally, and it starts a rebalance.

The stable topology is updated every time a rebalance operation ends and the coordinator determines that another rebalance is not necessary.

These rules ensures that at most one partition stays in AVAILABLE mode, and the other partitions enter DEGRADED mode.

When a partition is in DEGRADED mode, it only allows access to the keys that are wholly owned:

• Requests (reads and writes) for entries that have all the copies on nodes within this partition are honoured.

• Requests for entries that are partially or totally owned by nodes that disappeared are rejected with an `AvailabilityException`.

This guarantees that partitions cannot write different values for the same key (cache is consistent), and also that one partition can not read keys that have been updated in the other partitions (no stale data).

To exemplify, consider the initial cluster `M = {A, B, C, D}`, configured in distributed mode with `numOwners = 2`. Further on, consider three keys `k1`, `k2` and `k3` (that might exist in the cache or not) such that `owners(k1) = {A,B}`, `owners(k2) = {B,C}` and `owners(k3) = {C,D}`. Then the network splits in two partitions, `N1 = {A, B}` and `N2 = {C, D}`, they enter DEGRADED mode and behave like this:

• on `N1`, `k1` is available for read/write, `k2` (partially owned) and `k3` (not owned) are not available and accessing them results in an `AvailabilityException`

• on `N2`, `k1` and `k2` are not available for read/write, `k3` is available

A relevant aspect of the partition handling process is the fact that when a split brain happens, the resulting partitions rely on the original segment mapping (the one that existed before the split brain) in order to calculate key ownership. So it doesn’t matter if `k1`, `k2`, or `k3` already existed cache or not, their availability is the same.

If at a further point in time the network heals and `N1` and `N2` partitions merge back together into the initial cluster `M`, then `M` exits the degraded mode and becomes fully available again. During this merge operation, because `M` has once again become fully available, the ConflictManager and the configured EntryMergePolicy are used to check for any conflicts that may have occurred in the interim period between the split brain occurring and being detected.

As another example, the cluster could split in two partitions `O1 = {A, B, C}` and `O2 = {D}`, partition `O1` will stay fully available (rebalancing cache entries on the remaining members). Partition `O2`, however, will detect a split and enter the degraded mode. Since it doesn’t have any fully owned keys, it will reject any read or write operation with an `AvailabilityException`.

If afterwards partitions `O1` and `O2` merge back into `M`, then the ConflictManager attempts to resolve any conflicts and `D` once again becomes fully available.

Partitions are handled in the same manner as DENY_READ_WRITES, except that when a partition is in DEGRADED mode read operations on a partially owned key WILL not throw an AvailabilityException.

##### Current limitations

Two partitions could start up isolated, and as long as they don’t merge they can read and write inconsistent data. In the future, we will allow custom availability strategies (e.g. check that a certain node is part of the cluster, or check that an external machine is accessible) that could handle that situation as well.

#### 10.1.2. Successive nodes stopped

As mentioned in the previous section, Infinispan can’t detect whether a node left the JGroups view because of a process/machine crash, or because of a network failure: whenever a node leaves the JGroups cluster abruptly, it is assumed to be because of a network problem.

If the configured number of copies (`numOwners`) is greater than 1, the cluster can remain available and will try to make new replicas of the data on the crashed node. However, other nodes might crash during the rebalance process. If more than `numOwners` nodes crash in a short interval of time, there is a chance that some cache entries have disappeared from the cluster altogether. In this case, with the DENY_READ_WRITES or ALLOW_READS strategy enabled, Infinispan assumes (incorrectly) that there is a split brain and enters DEGRADED mode as described in the split-brain section.

The administrator can also shut down more than `numOwners` nodes in rapid succession, causing the loss of the data stored only on those nodes. When the administrator shuts down a node gracefully, Infinispan knows that the node can’t come back. However, the cluster doesn’t keep track of how each node left, and the cache still enters DEGRADED mode as if those nodes had crashed.

At this stage there is no way for the cluster to recover its state, except stopping it and repopulating it on restart with the data from an external source. Clusters are expected to be configured with an appropriate `numOwners` in order to avoid `numOwners` successive node failures, so this situation should be pretty rare. If the application can handle losing some of the data in the cache, the administrator can force the availability mode back to AVAILABLE via JMX.

#### 10.1.3. Conflict Manager

The conflict manager is a tool that allows users to retrieve all stored replica values for a given key. In addition to allowing users to process a stream of cache entries whose stored replicas have conflicting values. Furthermore, by utilising implementations of the EntryMergePolicy interface it is possible for said conflicts to be resolved automatically.

##### Detecting Conflicts

Conflicts are detected by retrieving each of the stored values for a given key. The conflict manager retrieves the value stored from each of the key’s write owners defined by the current consistent hash. The .equals method of the stored values is then used to determine whether all values are equal. If all values are equal then no conflicts exist for the key, otherwise a conflict has occurred. Note that null values are returned if no entry exists on a given node, therefore we deem a conflict to have occurred if both a null and non-null value exists for a given key.

##### Merge Policies

In the event of conflicts arising between one or more replicas of a given CacheEntry, it is necessary for a conflict resolution algorithm to be defined, therefore we provide the EntryMergePolicy interface. This interface consists of a single method, "merge", whose returned CacheEntry is utilised as the "resolved" entry for a given key. When a non-null CacheEntry is returned, this entries value is "put" to all replicas in the cache. However when the merge implementation returns a null value, all replicas associated with the conflicting key are removed from the cache.

The merge method takes two parameters: the "preferredEntry" and "otherEntries". In the context of a partition merge, the preferredEntry is the primary replica of a CacheEntry stored in the partition that contains the most nodes or if partitions are equal the one with the largest topologyId. In the event of overlapping partitions, i.e. a node A is present in the topology of both partitions {A}, {A,B,C}, we pick {A} as the preferred partition as it will have the higher topologId as the other partition’s topology is behind. When a partition merge is not occurring, the "preferredEntry" is simply the primary replica of the CacheEntry. The second parameter, "otherEntries" is simply a list of all other entries associated with the key for which a conflict was detected.

 EntryMergePolicy::merge is only called when a conflict has been detected, it is not called if all CacheEntrys are the same.

Currently Infinispan provides the following implementations of EntryMergePolicy:

Policy Description

MergePolicy.NONE (default)

No attempt is made to resolve conflicts. Entries hosted on the minority partition are removed and the nodes in this partition do not hold any data until the rebalance starts. Note, this behaviour is equivalent to prior Infinispan versions which did not support conflict resolution. Note, in this case all changes made to entries hosted on the minority partition are lost, but once the rebalance has finished all entries will be consistent.

MergePolicy.PREFERRED_ALWAYS

Always utilise the "preferredEntry". MergePolicy.NONE is almost equivalent to PREFERRED_ALWAYS, albeit without the performance impact of performing conflict resolution, therefore MergePolicy.NONE should be chosen unless the following scenario is a concern. When utilising the DENY_READ_WRITES or DENY_READ strategy, it is possible for a write operation to only partially complete when the partitions enter DEGRADED mode, resulting in replicas containing inconsistent values. MergePolicy.PREFERRED_ALWAYS will detect said inconsistency and resolve it, whereas with MergePolicy.NONE the CacheEntry replicas will remain inconsistent after the cluster has rebalanced.

MergePolicy.PREFERRED_NON_NULL

Utilise the "preferredEntry" if it is non-null, otherwise utilise the first entry from "otherEntries".

MergePolicy.REMOVE_ALL

Always remove a key from the cache when a conflict is detected.

Fully qualified class name

The custom implementation for merge will be used Custom merge policy

#### 10.1.4. Usage

During a partition merge the ConflictManager automatically attempts to resolve conflicts utilising the configured EntryMergePolicy, however it is also possible to manually search for/resolve conflicts as required by your application.

The code below shows how to retrieve an EmbeddedCacheManager’s ConflictManager, how to retrieve all versions of a given key and how to check for conflicts across a given cache.

``````EmbeddedCacheManager manager = new DefaultCacheManager("example-config.xml");
Cache<Integer, String> cache = manager.getCache("testCache");

// Get All Versions of Key

// Process conflicts stream and perform some operation on the cache
Stream<Map<Address, CacheEntry<Integer, String>>> conflicts = crm.getConflicts();
conflicts.forEach(map -> {
CacheEntry<Integer, String> entry = map.values().iterator().next();
Object conflictKey = entry.getKey();
cache.remove(conflictKey);
});

// Detect and then resolve conflicts using the configured EntryMergePolicy
crm.resolveConflicts();

// Detect and then resolve conflicts using the passed EntryMergePolicy instance
crm.resolveConflicts((preferredEntry, otherEntries) -> preferredEntry);``````
 Although the `ConflictManager::getConflicts` stream is processed per entry, the underlying spliterator is in fact lazily-loading cache entries on a per segment basis.

#### 10.1.5. Configuring partition handling

Unless the cache is distributed or replicated, partition handling configuration is ignored. The default partition handling strategy is ALLOW_READ_WRITES and the default EntryMergePolicy is MergePolicies::PREFERRED_ALWAYS.

``````<distributed-cache name="the-default-cache">
</distributed-cache>``````

The same can be achieved programmatically:

``````ConfigurationBuilder dcc = new ConfigurationBuilder();
dcc.clustering().partitionHandling()
.mergePolicy(MergePolicy.PREFERRED_ALWAYS);``````
##### Implement a custom merge policy

It’s also possible to provide custom implementations of the EntryMergePolicy

``````<distributed-cache name="the-default-cache">
</distributed-cache>``````
``````ConfigurationBuilder dcc = new ConfigurationBuilder();
dcc.clustering().partitionHandling()
.mergePolicy(new CustomMergePolicy());``````
``````public class CustomMergePolicy implements EntryMergePolicy<String, String> {

@Override
public CacheEntry<String, String> merge(CacheEntry<String, String> preferredEntry, List<CacheEntry<String, String>> otherEntries) {
// decide which entry should be used

return the_solved_CacheEntry;
}``````
##### Deploy custom merge policies to a Infinispan server instance

To utilise a custom EntryMergePolicy implementation on the server, it’s necessary for the implementation class(es) to be deployed to the server. This is accomplished by utilising the java service-provider convention and packaging the class files in a jar which has a META-INF/services/org.infinispan.conflict.EntryMergePolicy file containing the fully qualified class name of the EntryMergePolicy implementation.

```# list all necessary implementations of EntryMergePolicy with the full qualified name
org.example.CustomMergePolicy```

In order for a Custom merge policy to be utilised on the server, you should enable object storage, if your policies semantics require access to the stored Key/Value objects. This is because cache entries in the server may be stored in a marshalled format and the Key/Value objects returned to your policy would be instances of WrappedByteArray. However, if the custom policy only depends on the metadata associated with a cache entry, then object storage is not required and should be avoided (unless needed for other reasons) due to the additional performance cost of marshalling data per request. Finally, object storage is never required if one of the provided merge policies is used.

The availability mode of a cache is exposed in JMX as an attribute in the Cache MBean. The attribute is writable, allowing an administrator to forcefully migrate a cache from DEGRADED mode back to AVAILABLE (at the cost of consistency).

The availability mode is also accessible via the AdvancedCache interface:

``````AdvancedCache ac = cache.getAdvancedCache();