With the new asynchronous cross-site replication algorithm introduced in Infinispan 11, this release brings a long desired feature: conflict resolution.

It is possible to configure a merge policy where, in case of conflict between updates of different sites, the value can be merged. Some predefined merge policies can be found here.

See the docs for more information about conflict resolution.

Another small improvement has been made to cross-site replication in this release. When sites get requests targeting caches that don’t exist or aren’t started, sender sites stop retrying the requests, which takes the backup location offline. Administrators must then bring the sites back online and perform state transfer to sync possible out-of-date data.

This version includes a new version of the web console, including mainly fixes, but also the ability to filter between Strong and Weak counters and to remove counters from the list.

You can look at the release notes to see what has changed.

Our documentation has been updated with some additional content as well as improvements for clarity and technical accuracy, notably: * Infinispan Operator Guide * Server Guide * Guide to Cross-Site Replication * Security Guide

As always, the Infinispan team hope you find the documentation useful and complete. We’d love to hear from you and really value feedback from our community. If you think something is missing from the docs or spot a correction, please get in touch and we’ll get on it straight away.

You can look at the release notes to see what has changed.

We’re hard at work on new features, improvements and fixes, so watch this space for more announcements!

Please download, report bugs, chat with us, ask questions on StackOverflow.

Please download, report bugs, chat with us, ask questions on StackOverflow.

Please download, report bugs, chat with us, ask questions on StackOverflow.

Indeed, but version numbers are just that: numbers. We are still continuing our near-quarterly releases, but, from now on, these will be identified by major version numbers.

As usual we added new features, improved existing ones and prepared the groundwork for upcoming features.

As briefly mentioned above, Infinispan 12 will be our next release, scheduled for this autumn. We will be working on query/index improvements, backup/restore capabilities as well as the usual load of improvements, clean-ups across the board. We will keep you posted with development release and blogs about upcoming highlights. If you’d like to contribute, just get in touch.

Please download, report bugs, chat with us, ask questions on StackOverflow.

Starting with this release we are moving channels from a stable/preview structure to a micro-stream structure. This means you’ll get channels for each major.minor version of Infinispan.

For now version 1.1.x is available on the dev-preview channel but you should switch your Operator subscription to the 1.1.x channel before the next release to continue receiving updates.

If you use the Automatic Approval upgrade policy on OpenShift, your cluster is now running Infinispan Operator version 1.1.2 with the Infinispan 10.1.7.Final server image.

Try the simple tutorial for 1.1.x.

You can report bugs, chat with us, ask questions on StackOverflow.

The cross-site replication feature received two major improvements:

In a future update, Infinispan will allow you to set a custom conflict resolution algorithm.

Please download, report bugs, chat with us, ask questions on StackOverflow.

Please download, report bugs, chat with us, ask questions on StackOverflow.

If you installed the Infinispan Operator on Red Hat OpenShift with the Automatic Approval upgrade policy, your cluster should already be running the latest versions (Infinispan Operator 1.1.1 with Infinispan 10.1.2.Final).

We would like to hear opinions from you about the automated upgrade process, so get in touch if you have any issues or want to give any feedback.

Try the simple tutorial for the Operator, which has been updated for this version.

You can report bugs, chat with us, ask questions on StackOverflow.

Finally, a detailed list of issues and features for this version can be found here.

Infinispan 10.x servers have some significant changes to marshalling that impact Spring Boot users.

The default Marshaller for Infinispan 10.x is ProtoStream, which uses Protocol Buffers to provide extensible, language and platform neutral serialization.

Unfortunately ProtoStream does not currently work with Infinispan Spring Cache and Session support. As a result, Spring users in Remote Client/Server Mode must use the Java Serialization Marshaller and add classes to a Java serialization whitelist.

Add the following configuration properties:

infinispan.remote.marshaller=org.infinispan.commons.marshall.JavaSerializationMarshaller infinispan.remote.java-serial-whitelist=org.infinispan.tutorial.simple.spring.remote.*

The infinispan.remote.java-serial-whitelist property specifies the classes, or packages, that Java serialization can marshall. Separate multiple class names with a comma (,).

Note that, in previous versions, JBoss Marshaller was the default for Infinispan. Spring users can also use JBoss Marshalling, but it is deprecated as of Infinispan 10.x.

You can find these releases in the maven central repository.

Please report any issues in our issue tracker and join the conversation in our Zulip Chat to shape up our next release.

Enjoy,

The Infinispan Team

Infinispan Operator 1.1.0 is rated at the Full Lifecycle capacity level, which means the Operator now provides advanced cluster management capabilities and functionality to handle demanding workloads.

One of the key new features in this release is graceful shutdown, which lets you bring clusters down safely to avoid data loss.

During cluster shutdown, caches can passivate in-memory entries to persistent storage along with the internal Infinispan state that maps which nodes own which entries. When you bring Infinispan clusters back, all your data is restored to memory.

Check out the Graceful Shutdown docs for more information.

Graceful shutdown also enables the Infinispan Operator to perform reliable upgrades.

When a new version of the Infinispan Operator starts, it checks for running Infinispan clusters that were created by an older Operator version.

If the Operator detects a cluster that requires upgrade, it invokes a graceful shutdown on the cluster and then brings it back with the new Infinispan version.

You can perform upgrade manually or automatically with the Operator Lifecycle Manager on OpenShift.

Note that Operators installed via the OperatorHub on OpenShift Container Platform are managed by the Operator Lifecyle Manager.

This version of the Infinispan Operator delivers Cache and DataGrid services.

By default the Operator starts Infinispan clusters as Cache services, which provides a quick way to set up in-memory caching that stores data off-heap and keeps single copies of data in the cluster.

DataGrid services, on the other hand, are suited to more advanced use cases where you control and define the configuration that you need.

The Infinispan Operator simplifies cross-site replication set up with DataGrid services so you can back data up between separate Kubernetes or OpenShift clusters.

All you need to do is specify which type of external Kubernetes service to expose, the list of all backup locations, access secrets, and the local site name.

Find out more at: Cross-Site Replication

If you’re running on Openshift and have a service that serves certificates, the Operator automatically asks for certificates sets up TLS for your endpoint connections. Encrypted by default with zero effort!

Try the simple tutorial for the Operator, which has been updated for this version. The tutorial shows how to install the Operator manually, but it can also be installed via the Operator Hub on OpenShift.

You can report bugs, chat with us, ask questions on StackOverflow.

Finally, a detailed list of issues and features for this version can be found here.